JP2018077900A - Sns system, bank system, and credit card company system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To confirm payment of event participation costs of a participant on the basis of notification from a financial institution by making an SNS and a system of the financial institution cooperate with each other.SOLUTION: An SNS system accepts event registration from a user as an event master, and transmits notification for recruiting a participant of the event to a participation candidate, and accepts the participant of the event. The participant can select bank transfer or a credit card as a payment method of participation costs of the event, and the SNS transmits a payment request of a transfer request or a card settlement request to the participant on the basis of the selection. A system of the financial institution accepts the payment of the event participation costs based on the payment request from a site of the Internet, and when the user executes payment of the participation costs, transmits the payment information together with an official symbol of the financial institution to the SNS. The SNS transmits payment confirmation of the participation costs of the participant to the event master when receiving the official symbol and participant's payment information based on the payment request from the SNS from the financial institution.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an event participation fee payment system and a payment method thereof. In particular, the present invention relates to an event participation fee payment system for confirming payment of event participation fee from a financial institution and a payment method thereof.

  Conventionally, a number of systems for supporting the secretary's work (event reservation, contact to participants, collection, clearing, financial reporting, etc.) at events such as banquets and meetings have been disclosed. For example, in Patent Document 1, a restaurant information search unit that searches for a restaurant and transmits a result to the secretary terminal, a banquet information registration unit that registers information about a restaurant and a date and time candidate, a restaurant and a date and time A participant sending means for sending the candidate's e-mail to the participant, information on the date and time of the banquet selected by the participant, and objective evaluation information for the restaurant candidate are added and summed up The first reservation means for transmitting a banquet reservation e-mail to the restaurant determined by the secretary, and the determined date and time and restaurant information are transmitted to the participant after the means and the answer deadline. A banquet reservation support system having a determination transmission means is described.

  Further, in Patent Document 2, in the secretary business support system for meetings using the Internet, the date and place of the meeting are determined by using the system of the present invention when the secretary determines a hotel or restaurant as a meeting venue.・ Enter participants and membership fees in a standard format and send data from the hotel or restaurant terminal to the meeting information posting server. Then, the server that has received the data automatically sets up a home page that guides the meeting, so that the home page can be immediately viewed from anywhere and the meeting information can be obtained. In addition, if you look at this website and want to join the meeting, you can apply for participation and pay membership fees via the Internet.

JP 2006-323805 A Japanese Patent Laid-Open No. 2002-092271

  The banquet reservation support system described in Patent Document 1 supports the organizer of a banquet or meeting to make a reservation for a store or date, while the secretary consults with other participants about the store, date, etc. It does not support membership fee collection, liquidation, or financial reporting, which is a major burden for the secretary. In addition, the secretary business support system described in Patent Document 2 enables participants to apply for participation and pay membership dues using an Internet homepage, and collect money using a deposit account of a financial institution. It aims to be efficient. However, payment methods for membership fees are limited to credit cards, and it is necessary to construct a new meeting settlement information server dedicated to making payment requests to credit card companies on behalf of the hotel or restaurant serving as the meeting venue. It was.

  In recent years, calls for events such as banquets and meetings have more frequently used SNS (Social Networking Service) such as Facebook (registered trademark) than conventional e-mails. In SNS, friends, acquaintances, and members are often registered with their attributes, and various communication methods between members are prepared, so that the user who is the organizer will be notified of event holding and participation confirmation This is because it is convenient because it is possible to consistently contact many people at once, such as processing at the time of cancellation. Therefore, the need for dedicated systems such as Patent Documents 1 and 2 is diminishing. However, even if SNS is used, it has not been possible to confirm the collection and payment of membership fees for events. This is because there is no means for connecting the SNS and the financial institution system. For this reason, in many cases, the current situation is that the secretary manually performs event collection, payment confirmation work, and the like.

  Therefore, in view of the problems as described above, an object of the present invention is to provide an event participation fee payment system that can link an SNS and a financial institution system and confirm payment of an event membership fee.

  In order to solve the above problems, the event participation fee payment system and the event participation fee payment method of the present invention provide the following solution.

  In the first aspect of the present invention, an SNS system, a bank system, an event master terminal of a user who is a user of the SNS system and is an event organizer or secretary, and a participant terminal that is a participant of the event Is connected to the network and pays and confirms the event participation fee. The SNS system accepts the event information from the event master terminal and registers it in the event information storage means. An event registration unit, a participant recruitment transmission unit that sends a notification for recruiting participants of the event to the participant terminal when the event is registered, and the participant terminal that has received the recruitment notification , A participant acceptance unit that accepts participants in the event, and a bank transfer method for the participant to pay the participation fee for the event If selected, a payment notification indicating that the participant has made a transfer based on the transfer request from the banking system and a participation fee payment request unit that transmits the transfer request to the participant terminal. A payment information confirmation unit that receives the official symbol of the bank and transmits the payment notification to the event master terminal, and the bank system executes the transfer and a transfer reception unit that receives a transfer based on the transfer request And a payment information transmission unit that transmits the payment information of the participant to the payment information confirmation unit together with the official symbol of the bank after the transfer is executed.

  In the second aspect of the present invention, an SNS system, a credit card company system, an event master terminal of a user who is a user of the SNS system and is an event organizer or secretary, and a participant of the event An event participation fee payment system connected to a certain participant terminal via a network and paying and confirming the event participation fee, wherein the SNS system receives the event information from the event master terminal, An event registration unit for registering in the storage means, a participant recruitment transmission unit for sending a notification for recruiting participants of the event to the participant terminal when the event is registered, and a notification of the recruitment A participant reception unit for accepting a participant of the event from the participant terminal, and the participant participating in the event; When a credit card is selected as the payment method of the fee, the participant pays the card payment request from the participation fee payment request unit that transmits the card payment request to the participant terminal and the system of the credit card company. A payment information confirmation unit that receives a payment notification indicating that payment has been made based on the official symbol of the credit card company and transmits the payment notification to the event master terminal, and the credit card company system includes: A member store information confirmation unit that confirms that the business operator of the event venue is a member store of the credit card, and an authorization processing unit that receives a request from the member store information confirmation unit and approves the use of the credit card. And after the approval of the use of the credit card, together with the official symbol of the credit card company, the participant's And payment information transmitting unit that transmits the payment information to the payment information confirmation unit, characterized in that it comprises a.

  In the event participation fee payment system, the participation fee payment requesting unit includes an ID of the event, a user ID of the SNS system of the participant, and link information to an Internet site of a financial institution designated by the participant. You may comprise so that the participation fee payment request which contains may be transmitted to the said participant terminal.

  In the event participation fee payment system described above, the SNS system may include a payment information totaling unit that totals the payment information for an accounting report after the event ends.

  In the above event participation fee payment system, the event may include a banquet, a meeting, a donation solicitation, a gift of congratulations, a joint purchase of a lottery ticket, and a fee collection for an event organized by an organization.

  In the third aspect of the present invention, an SNS system, a financial institution system, an event master terminal of a user who is a user of the SNS system and is an event organizer or secretary, and a participant who is a participant of the event An event participation fee payment method for paying and confirming the event participation fee connected to a terminal via a network, wherein the event information storage means accepts the event information from the event master terminal in the SNS system. Registering, after registering the event, transmitting a notification for recruiting participants of the event to the participant terminal; and from the participant terminal receiving the recruitment notification, Accepting and, if the participant has selected a payment method for the event participation fee, the payment method A payment request corresponding to the financial institution to the participant terminal, a notification of the payment information of the participant together with the official symbol of the financial institution from the financial institution system, and the notification to the event master Transmitting to the terminal, in the system of the financial institution, accepting payment of the participation fee based on the payment request, executing the payment request, and after executing the payment, Transmitting the participant's payment information together with the official symbol to the SNS system.

  ADVANTAGE OF THE INVENTION According to this invention, the system of a SNS and a financial institution can be cooperated and the event participation fee payment system which can confirm payment of the membership fee of an event can be provided.

It is a figure which shows the basic concept of this invention. It is a figure which shows the function structure of the event participation fee payment system which concerns on 1st embodiment of this invention. It is a figure which shows the function structure of the event participation fee payment system which concerns on 2nd embodiment of this invention. It is a figure which shows the data structure of event master DB11 which concerns on embodiment of this invention. It is a figure which shows the process sequence between each terminal and each system in the event participation fee payment system which concerns on embodiment of this invention. It is a figure which shows the specific example of an event registration screen and an event participation application screen. It is a figure which shows the specific example of the transfer request screen in the case of paying a participation fee with a bank transfer, and a bank transfer screen. It is a figure which shows the specific example of the card payment request screen in the case of paying a participation fee with a credit card, and the payment information input screen in a card company system. It is a figure which shows the specific example of the event master top screen in an event master terminal, and an event master total screen. It is a figure which shows the specific example of the information relevant to the event of a user basic information screen. It is a figure which shows the contribution event registration screen and its total screen as a specific example of an event. It is a figure which shows a celebration event registration screen and its total screen as a specific example of an event. It is a figure which shows the lottery joint purchase event registration screen and its total screen as a specific example of an event. It is a figure which shows an examination fee collection event registration screen and its total screen as a modification of an event.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments for carrying out the present invention (hereinafter referred to as embodiments) will be described in detail with reference to the accompanying drawings. In the subsequent drawings, the same numbers or symbols are assigned to the same elements throughout the description of the embodiments. In the functional configuration diagram, an arrow between functional blocks represents a data flow direction or a process flow direction. In the process flow diagram (flowchart), the processing order of each step may be changed as long as the relationship between the input and output of each step is not impaired.

(Basic concept)
FIG. 1 is a diagram showing the basic concept of the present invention. An organizer or organizer of an event such as a banquet or a meeting (hereinafter referred to as an event master) first registers an event from the event registration screen 100 on the SNS. The registered event information is stored in the event master DB 11 on the SNS (step 1). At this time, the event registration screen 100 can include a list of participation candidates who call for participation in the event. Participation candidates may not necessarily be SNS users. When the event registration is completed and the “Send to Participant” button is pressed, if the candidate is a user of the same SNS, an event participant recruitment notice will be posted on the top screen of the candidate and the event Participant recruitment email is sent to the email address of the candidate for participation (step 2). In addition, when a participating candidate is not an SNS user, only mail is transmitted.

  A candidate for participation decides whether to participate by looking at the contents of the event from the event participant recruitment screen 200. When a candidate for participation presses the “participate” button from this screen, it is registered as “participant” in the event master DB 11 which is an event information storage means (step 3), and the event master screen is also joined to the event top screen 110 of the event master. It is displayed that the candidate has announced participation (step 4). Although illustration is omitted, the event participant recruiting screen 200 allows the participant to select a payment method such as an event participation fee or a membership fee. The payment method can be selected from bank transfer, credit card, or cash payment on the day.

  The event master confirms the participant. If the participant has selected payment by bank transfer or credit card, the event master transmits a payment request to the participant from the payment request screen 120 (step 5). . This payment request is registered in the event master DB 11, and on the SNS side, payment schedule information for the participation fee is transmitted for each participant to the affiliated financial institution (step 6). On the financial institution side, as a subset of the event master DB 11, an event slave DB 21 that is an event information auxiliary storage means including only data necessary for the financial institution side is provided. The event slave DB 21 includes an event slave DB 21 for each event and each participant. Stores payment schedule information. At this point, if the participant has designated a financial institution to use for payment, the payment schedule information will be sent only to that financial institution, but if no financial institution has been designated, all partner financial institutions will be informed. , The payment schedule information is transmitted. The event master DB 11 and the event slave DB 21 are always synchronized with the latest information.

  After receiving the payment request from the event master, the participant logs in to the WEB page of the financial institution with which he / she is dealing, and pays the event participation fee from the WEB page of the financial institution (step 7). The transfer screen 210 shown in the figure shows a scene in which a participant accesses Internet banking of a bank and transfers a participation fee. When the participant designates the financial institution in advance, the transition to the WEB page of the financial institution from the notification of the payment request may be allowed. At this time, the account number and amount of the transfer destination may be automatically input on the WEB page of the financial institution. After confirming the contents of the transfer screen 210, the participant inputs a password or a password for the transfer, and presses the “transfer” button to complete the event payment. When the payment method is a credit card, it is basically the same, but will be described later.

  The financial institution is notified that the participant has completed payment (step 8). In the financial institution, in order to notify the SNS side of the payment confirmation, on the event top screen 111 of the event master, an official symbol of the financial institution (hereinafter referred to as the financial institution confirming that the payment has been confirmed). A payment confirmation notice is posted (step 9). This paid mark is created with a special image that cannot be counterfeited, and the SNS side authenticates that this payment confirmation notice has been posted by a financial institution, and then the event master event top screen. 111. By doing in this way, the event master can know by the financial institution that the participant has been surely paid. Therefore, there is no need to confirm the bank account of the transfer destination. This is particularly useful in events where many people participate.

(Functional configuration)
FIG. 2 is a diagram showing a functional configuration of the event participation fee payment system (hereinafter, this system) according to the first embodiment of the present invention. In the first embodiment, a case where the financial institution is a bank will be described. The SNS system 10 is connected to an event master terminal 31 of an event master that is a user and a participant terminal 32 of a participant who is also a user via the Internet, and a bank system on the Internet or a dedicated network. 20 is connected. The event master terminal 31 and the participant terminal 32 are configured by a general PC, a smartphone, or the like, and there is no distinction in hardware. Any SNS user can be an event master or an event participant. However, it is assumed that the event master separately communicates with the event venue terminal 33 of the event venue (hotel, banquet hall, etc.) registered by the event master terminal 31.

  The SNS system 10 is a system in which an event support function is added to an existing SNS system in cooperation with a bank system. Typical configuration examples of the SNS system include an event master DB 11, an event information synchronization unit 12, an event registration unit 13, a participant recruitment transmission unit 14a, a participant reception unit 14b, a participation fee payment request unit 15, and a payment information confirmation unit. 16 and a payment information totaling unit 17.

  The event master DB 11 is an event ID, an event master user ID, user information thereof, an event venue, an event participation fee payment destination, the number of participants, a user ID for each participant, a participation status, a payment method for the participation fee, etc. Contains information. A specific example of data stored in the event master DB 11 will be described later with reference to FIG.

  The event information synchronization unit 12 has a role of always synchronizing the event master DB 11 on the SNS side and the event slave DB 21 on the bank system 20 side. Specifically, exchange of update information and exclusive access control at the time of writing are performed so that the update information (data communication date and time and data thereof) of both DBs always match. Since the database synchronization method itself is a known technique, its details are omitted.

  The event registration unit 13 accepts input of event information from the event master terminal 31 and stores it in the event master DB 11. The registration and change of the event information is naturally synchronized with the event slave DB 21 on the bank system side, but it is not necessary to synchronize information not used on the bank side.

  When the event is registered, the participant recruitment transmission unit 14a transmits a participant recruitment notification to the participants in the participation candidate list. Participant reception part 14b receives the information of the participant who applied for participation with respect to the event which transmitted the participant recruitment notice, and stores it in event master DB11. The participant information may include a message for the event master, an evaluation after the end of the event, and the like in addition to the participant user ID and the payment method of the participation fee.

  The participation fee payment request unit 15 generates a payment request according to the payment method selected by the participant. In the case of the figure, since it is assumed that the participant has selected bank transfer, a list of bank transfer participants is generated and transmitted to the event master. The event master confirms this participant list, and if there is no excess or deficiency, the event master sends a transfer request to all participants who wish to make a bank transfer. The participation fee payment request at this time includes the event ID, the amount of the participation fee, and the account number of the transfer destination. In addition, when the participant designates the bank to which the transfer is made, the link information (URL) of the bank's Internet site, the event ID, and the participation information if the participant is an SNS user in the payment request notification. The user ID on the SNS may be included so that the participant can transition from the payment request notification to the bank WEB page and log in directly to the bank site. Information such as an event ID, a user ID on the SNS, and a transfer account may be automatically delivered to the bank site at this time. The bank account of the event master itself may be used as the transfer account. In this case, it is necessary to settle the event master at a later date from the event master whose cost has been changed. The case where the participant's payment method for the participation fee is a credit card will be described later with reference to FIG.

  The payment information confirmation unit 16 receives a payment notification from the bank system 20 when the participant who has selected the bank transfer actually performs the transfer, writes the information in the event master DB 11, and simultaneously notifies the event master. . Specifically, this notification is displayed on the event top screen of the event master.

  The payment information totaling unit 17 reads the event master DB 11 in response to a request from the event master, and totals the payment information of the event. The payment information totaling unit 17 can, for example, extract and sort paid marks, perform totaling for each financial period in which the participant has paid, and the like. In addition, even if the participant pays in cash, the data can be added to the total by manually inputting the data to the event master. The counting results are mainly transmitted to the event master, but some information may be transmitted to the participants. This function is useful when the event master makes an accounting report after the event ends.

  Next, the functional configuration on the bank system 20 side will be described. The bank system 20 is a system in which an event support function is added to an Internet banking system [also called an EB (Electronic Banking) system] provided by a bank in cooperation with an SNS. A typical configuration of the bank system includes an event slave DB 21, an event information synchronization unit 22, a transfer acceptance unit 23, a transfer processing unit 24, and a payment information transmission unit 25.

  The event slave DB 21 receives and stores information used on the bank side from the event master DB 11 described above. The event information synchronization unit 22 controls the synchronization between the databases in cooperation with the event information synchronization unit 12 on the SNS side.

  The transfer accepting unit 23 is the same as the transfer process in the Internet banking of the bank system 20, but allows the participant to input the event ID and the user ID on the SNS on this transfer screen. Here, the event ID is common to both systems, but the user ID is naturally different between the SNS and the bank system. The transfer acceptance unit 23 can search the event slave DB 21 based on the event ID and the user ID on the SNS, and can automatically input the amount of the participation fee and the transfer destination account. Of course, since the transfer request received by the participant includes the amount and the transfer account, the participant may manually input them when making the transfer. In addition, when the bank designates the bank to transfer in advance, the event request URL for the bank is described in the transfer request notification received by the participant. When logging in to the system 20, a screen on which information necessary for the transfer is automatically input may be displayed.

  The transfer processing unit 24 is a general account system of a bank, and executes a transfer (transfer of funds between accounts) received by the transfer receiving unit 23. If the transfer process is normally performed, the result is written in the event slave DB 21. The transfer result may be returned to the transfer receiving unit 23, and the transfer receiving unit 23 may write the transfer result in the event slave DB 21.

  The payment information transmission part 25 transmits the information to the payment information confirmation part 16 by the side of SNS, when the transfer regarding event participation fee is normally performed. Specifically, the payment information transmission unit 25 on the bank side transmits the event ID and the user ID on the SNS of the participant to the payment information confirmation unit 16 on the SNS side together with the company's official paid mark. Then, the payment information confirmation unit 16 on the SNS side displays the paid mark together with the participant ID and the payment amount on the top screen of the event master.

  FIG. 3 is a diagram showing a functional configuration of the event participation fee payment system according to the second embodiment of the present invention. In the second embodiment, a case where the financial institution is a credit card company will be described. The SNS system 10 is connected to the event master terminal 31 and the participant terminal 32 via the Internet, but is connected to the credit card company system 20A via the Internet or a dedicated network. Below, only a different part from 1st embodiment is demonstrated. The first embodiment and the second embodiment are not selectively used, and both can be provided in the present system.

  In the SNS system 10, a function for the participation fee payment requesting unit 15 to make a request for card settlement is added. The participation fee payment requesting unit 15 transmits a payment request with a credit card to the participant terminal 32 when the participant has selected payment of the participation fee with a credit card. The payment request information at this time includes the event ID, the user ID on the participant's SNS, and the amount of the participation fee. The participant who has received the settlement request logs in to the WEB page of the system of the credit card company with which he / she has contracted, and settles this payment. The payment information confirmation unit 16 receives a payment notification that the card payment has been completed.

  Credit card WEB systems are usually used to check card usage, check invoices, change payment methods (afterwards, revolving payments or change to installment payments). Support function is added, so card payment for event participation fee is possible. In other words, the credit card company system normally receives an authorization request for a card from a merchant terminal and determines whether or not the settlement is acceptable (performs approval of whether or not the card can be used). However, in this system, it plays the role of substituting payment between the participant and the member store (in this case, the hotel or store serving as the event venue).

  Therefore, as shown in the figure, the credit card company system 20A includes a member store information confirmation unit 26 and an authorization processing unit 27. The member store information confirmation unit 26 reads the event slave DB 21 when a login for payment is made from the participant terminal 32 via the SNS, and whether the event ID and the user ID on the SNS are registered. Confirm.

  Here, the event ID is common to both systems, but the user ID is naturally different in both systems. In this system, the participant can settle the event participation fee in the credit card company system 20A by inputting the event ID, the user ID on the SNS, the credit card number, the password for settlement, or the password. it can. For this reason, the merchant information confirmation unit 26 on the card system side reads information on the event based on the event ID input from the event slave DB 21 and the user ID on the SNS, and the event venue included in the event information The ID, name, address, etc. of the facility (hotel, store, etc.) to be read are read out. If the facility ID, name, address, etc. are registered as a member store of the credit card, the information is referred to the member store system 40 provided in the facility for confirmation. As a result of this inquiry, if the facility is a member store of the company, it is assumed that the participant has made a card payment from the WEB page of the member store system 40, and the authorization processor 27 approves the card. Ask.

  The authorization processing unit 27 confirms the card number, password, name holder, expiration date, usage limit, etc., in the same way as a card approval request from a normal member store terminal (POS terminal, etc.), and the card can be used. If so, approve the settlement. Further, in the case of an approval request from the member store information confirmation unit 26, if there is no problem with the approval, the approval result is written in the event slave DB 21. The event information synchronization unit 22 on the card system side transmits this approval result (DB update information) to the event information synchronization unit 12 on the SNS side so that the event slave DB 21 and the event master DB 11 are always synchronized. This is the same as the case of 2. Then, if the use of the card is approved by the authorization processing unit 27 (if the approval of the card payment of the user ID of the event ID in the event slave DB 21 is described), the payment information transmission unit 25 on the card system side is described. ), The event ID and the user ID on the participant's SNS are transmitted to the payment information confirmation unit 16 on the SNS side together with the company's official paid mark. On the SNS side, this paid mark is displayed on the top screen of the event master together with the participant ID and the payment amount. In the above explanation, the participant pays directly to the member store with a credit card, but the credit master itself can also be a member store as a private business owner. On the other hand, you pay with a credit card. In other words, the event master itself generates billing data for the credit card company as a member store, and the credit card company debits the billing data from the participant's credit card payment account.

  FIG. 4 is a diagram showing a data structure of the event master DB 11 according to the embodiment of the present invention described above. As shown in the figure, the event master DB 11 is divided into event information 11 a and event information 11 b as event contents, in addition to an event ID unique to the event. The event information 11a is normally input at the time of event registration, but can be updated thereafter. Participant information 11b changes from moment to moment in response to a participant's application.

  The event information 11a includes event master information 11a1 (user ID, mail address, telephone number, etc.) of the user who has become the event master. When the event master changes the participation fee, the event master's own bank account may be encrypted and included. Further, the event information 11a includes event venue information 11a2, and the event venue information 11a2 includes an event date and time, a venue, a participation fee, a method of accepting payment of the participation fee (bank transfer, credit card, cash, etc. ) When accepting a bank transfer, the account number of the transfer destination and the event invitation period are stored.

  The participant information 11b includes the number of participants who have announced participation at the present time, a user ID for each participant, a participation status indicating whether or not they intend to participate, a payment method for the participation fee, and a payment status indicating the payment status. Stored. The payment method may include the name of the bank serving as the transfer source and the name of the credit card. In the case of bank transfer, one of “preparing for transfer request”, “during transfer request”, and “transferred” is stored in the payment status. In the case of credit card payment, in addition to “Preparing for payment request”, “Requesting payment”, “Payment completed”, if you can accept cancellation after payment, “Refund required”, “Refunded” Etc. are stored.

  The functional configuration of the system described above is merely an example, and one functional block (database and function processing unit) may be divided, or a plurality of functional blocks may be configured as one functional block. . Each function processing unit reads a computer program stored in a storage device such as a ROM (Read Only Memory), flash memory, SSD (Solid State Drive), or hard disk by a CPU (Central Processing Unit) built in the device This is realized by a computer program executed by the CPU. That is, in each function processing unit, this computer program reads and writes necessary data such as a table from a database (DB; Data Base) stored in a storage device or a storage area on a memory, and may be related in some cases. This is realized by controlling hardware (for example, an input / output device, a display device, and a communication interface device). Further, the database (DB) in the embodiment of the present invention may be a commercial database, but it simply means a collection of tables and files, and the internal structure of the database itself is not questioned.

  FIG. 5 is a diagram showing a processing sequence between each terminal and each system in the event participation fee payment system according to the embodiment of the present invention. In this figure, the first embodiment in the case where the financial institution is a bank will be described. However, the second embodiment is basically the same as the first embodiment. Will be explained last. In the description of this figure, the event master terminal 31 is simply called a master terminal, the SNS system 10 is called an SNS, the bank system 20 is called a bank system, and the participant terminal 32 is called a participant terminal. In the following, it is assumed that the process from event master event registration to participant participation application has already been completed.

  First, in step S10, the master terminal selects a bank transfer applicant from event participants, and transmits a transfer request to the SNS. At this time, the list of participants who wish to make a bank transfer is automatically generated by the SNS based on the information at the time of the participant's participation application, but the event master changes the list of participants who want to make a bank transfer at any time. be able to. This is because some participants may contact the event master by another method (telephone etc.) before contacting the SNS when changing the payment method or canceling the event participation itself.

  When the SNS receives this transfer request from the master terminal, in step S20, the payment status in the event master DB 11 is updated to “during transfer request” and transmitted to the bank system. In the bank system, in step S30, the event slave DB 21 is updated to the latest state, and the database is synchronized. Further, in step S21, the SNS acquires the email address of the participant who wishes to transfer the bank from the event master DB 11, and transmits a transfer request email to the participant terminal. At this time, it goes without saying that this request notification is also described on the event top screen of each participant.

  When the participant terminal receives the transfer request in step S40, the participant terminal is requested to log in to the net banking contracted by the participant and select “event transfer” displayed after login (step S41). The event transfer is a dedicated transfer screen prepared for paying an event participation fee in cooperation with the SNS. The event transfer screen requires input of the event ID and the user ID on the SNS on the normal transfer screen, but when logging in to the bank system from the URL linked from the transfer request screen on the SNS, the event ID and the user on the SNS The ID is automatically entered.

  In the banking system, when it is detected that the participant who has logged in to the Internet banking of the bank has selected event transfer, the transfer amount of the event participation fee is transferred from the event slave DB 21 based on the input event ID and the user ID on the SNS. A transfer account is acquired and a transfer screen is generated (step S31). After confirming the contents of this transfer screen, if the participant is OK, the participant inputs the transfer PIN or password and transmits a transfer execution request to the bank (step S42).

  The bank system (account system) that received the transfer execution request executes the transfer in step S32. Then, the payment status of the participant in the event slave DB 21 is updated, and at the same time, an official paid mark is also transmitted to the SNS (step S33).

  The SNS updates the event master DB 11 upon receiving this paid mark in step S22, and the updated information in the event master DB 11 in step S23, that is, that the participant has completed the transfer and has confirmed that the bank system has confirmed. Is transmitted to the master terminal together with the paid mark. Finally, the master terminal confirms the official paid mark from the bank in the event information displayed on the event top screen, and can know that the participant has surely paid the participation fee (step S11). In this way, the process up to the completion of the transfer of the participant is completed in response to the transfer request from the event master.

  In FIG. 5, the first embodiment in the case where the financial institution is a bank has been described. However, in the second embodiment in which the financial institution is a credit card company, the bank system 20 is changed to the credit card company system 20A. If the transfer request is replaced with a settlement request, the transfer screen is replaced with a settlement screen, and the transfer execution request is replaced with a card approval request, the same is basically true. However, in the above step S31, before generating the payment screen, the above-mentioned member store system 40 is confirmed with respect to whether or not the operator operating the event venue described in the event information is a member store of the credit card. A step is added (see the explanation of the member store information confirmation unit 26 in FIG. 3).

FIG. 6 is a diagram showing specific examples of an event registration screen and an event participation application screen.
An event registration screen 100 shown in the figure is a screen used when an event master registers an event. This screen can be selected from a menu in the SNS. As event registration information, an event name, a date and time, a venue, a participation fee, a period for recruiting participants, and a payment method for accepting participation fees are selected. Then, a user recruitment list is created from the SNS friend list or a separately imported list. When registration of the event is completed, an event ID is assigned from the SNS, and when a “recruit participant of this event” button is pressed, a participant in the participation recruitment list is notified.

  Event participant recruitment screen 200 is transmitted to the participation candidate, and after confirming the contents of the event, the participant candidate selects a participation fee payment method and participates in “participate in this event”. "Button is registered as a participant in the event master DB 11, and at the same time, the event master is notified of this.

  FIG. 7 is a diagram showing a specific example of a transfer request screen and a bank transfer screen when the participation fee is paid by bank transfer. The event master transmits a “transfer request” after confirming the participant who transmits the transfer request after inputting the bank account number, the holder, and the transfer amount of the transfer destination from the payment request screen 120 (transfer request screen). The bank account number and the holder of the transfer destination may be input as defaults from the user basic information of the event master. The list of participants to send the transfer request is generated from the SNS friend or acquaintance list or by importing a separately prepared candidate file, but the event master should change the list if there is any excess or deficiency Can do.

  The participant who has received the transfer request logs in to the Internet banking of the bank with which he / she has contracted, and inputs the event ID and his / her user ID on the SNS from the event participation fee transfer screen 210 as shown in the figure. The event ID and user ID may be manually entered, but when logging in to the bank's Internet banking from the URL described in the transfer request, the event ID and user ID may be automatically entered. Participants confirm the displayed withdrawal account and transfer account and the transfer amount, and perform the transfer.

  FIG. 8 is a diagram showing a specific example of a card payment request screen when paying the participation fee with a credit card and a payment information input screen in the card company system. The event master requests the participant who has selected the card settlement to pay the participation fee from the card settlement request screen 121 (payment request screen) as illustrated.

  The participant who received the card payment request inputs the card information from the event participation fee card payment screen 211 as shown in the figure (assuming that the event ID and SNS user are automatically input), and after confirming the payee , Enter the number of payments and the password or password for payment, and make a payment.

  FIG. 9 is a diagram showing a specific example of an event top screen and an event master total screen on the event master terminal. The event top screen is a top screen in the SNS of the event master, and displays all information related to events for which the event is hosted in time series. On the event top screen 112 shown in the figure, in addition to an event participant's participation expression, non-participation expression, and cancellation request, payment confirmation of participation fee from the financial institution is displayed together with the official paid mark of each financial institution. On this screen, it is possible to provide a function for sorting only the pay marks or sorting by each participant.

  The event master totaling screen 140 is a screen having a function of counting and displaying various types of event information. Specifically, as shown in the figure, the number of participation candidates (persons who have called for participation), the actual number of participants, the number of absent persons, the number of unanswered persons, and the breakdown of each number are displayed. In addition, the number of payment confirmations for each financial institution and its breakdown, the number of cancelers after card settlement and their breakdown (subject to be refunded), and the number of unpaid persons despite the payment request and their breakdown are displayed. . A reminder is sent to the unpaid person, but if the payment is still not made, it may be treated as non-participation. Further, when the “Create Accounting Report” button at the bottom of the screen is pressed after the event is finished, a payment report for the participant is automatically created by the payment information totaling unit 17.

  FIG. 10 is a diagram illustrating a specific example of information related to an event on the user basic information screen. In SNS, it is common to register a user's profile as the basis for creating a network, but in this system, in addition to the user's personal information such as origin and age, the number of times he served as an event master, received as an event master. All information related to the event has been added to the basic information, such as the number of evaluations and comments, the number of participants who participated in the event as a participant and their breakdown, and the number and breakdown of payments that have been completed and those that have not been paid It can be displayed on the user basic information screen 130 as shown. Whether or not to disclose this information depends on the user's settings, but by making it public to other users, what kind of event you are participating in, what kind of event you are interested in, as an event master More opportunities are given to know the user's desires, such as whether they are active.

(Other specific examples of events)
According to this system, payment and confirmation of event participation fees such as banquets and meetings can be performed smoothly, but the events handled by this system are not limited to banquets and meetings, but can be applied to various events involving payment. Can do. Hereinafter, a specific example of such an event will be described.

  FIG. 11 is a diagram showing a donation event registration screen and its totaling screen as specific examples of events. Unlike banquets and meetings, donations generally do not have elements such as event venue reservations, card payments, contact with participants, cancellation of participation, and financial reporting, but the system mechanism can be applied as is. In other words, any user of this system can call for private and public donations of various sizes. The initiator of the donation becomes an event master in this system, and registers the event of donation from the event registration screen 101 as shown in the figure. The event information to be registered is basically the same as in the case of a banquet or meeting, but the event details information clearly states that only the total amount of donations will be disclosed to the participants. In addition, not only friends and acquaintances but also all users of SNS can be targeted for recruitment.

  Generally, there is some anxiety about donating to donations hosted by individuals or unknown groups, but it is sponsored by users who have a good track record as event masters by looking at the basic user information mentioned above. If it is known that the donation is being made, other users can donate with confidence. The user who hosts the donation event may be required to disclose the part related to the event of the user basic information. In addition, if this system is used, payment confirmation can be confirmed with an official paid mark from a financial institution. As shown in the figure, the number of donors and the total amount of donations are displayed on the event master totaling screen 141 at the end of the donation or every predetermined period, and notified to the event master. Then, when the event master presses the “Send to Fundraiser” button at the bottom of the screen after the end of the fundraising activity, the number of fundraisers and the total donation amount are transmitted to all the fundraiser users as a report of the fundraising activity.

  FIG. 12 is a diagram showing a celebration event registration screen and its totaling screen as specific examples of events. This screen is an example of registering congratulations for admission, graduation, employment, marriage, childbirth, etc. as an event of this system. The event information to be registered from the event registration screen 102 of the celebration is input as shown in the figure, but if the user ID of the destination of the celebration (gift destination) is described in the event detailed information, participation is possible. A person can send a congratulatory message through this system. In addition, since there are cases where gifts are half-turned from the gift recipient, it is clearly stated that the breakdown of the gift will be disclosed to the gift recipient.

  On the event master summary screen 142 of the celebration event, the number of participants of the celebration and its breakdown button are displayed, but even if the breakdown button is pressed, the details of who paid how much are not disclosed to the event master. You may do it. Of course, when the event master presses the “Send to gift recipient” button, all of the details are disclosed to the gift recipient.

  FIG. 13 is a diagram showing a lottery group purchase event registration screen and its total screen as specific examples of events. The lottery group purchase event registration screen 103 shown in the figure is an example in which a lottery group purchase is registered as an event of the present system. On this screen, event information as shown in the figure is entered, but for the event detailed information, it is selected that details of the investment will be disclosed to all investors. You can also choose to disclose only the total amount of investment to investors.

  In the event master total screen 143 in the lottery joint purchase event, the number of participants (contributors) and their breakdown buttons are displayed. The breakdown button indicates that the above event detailed information indicates only the total amount of capital contribution to the investors. In the case of disclosure, it can be displayed only on the event master (or a user who has actually purchased lottery tickets together). This is in consideration of the privacy of investors, but since the breakdown of each investor's investment is recorded in the payment confirmation notice of the financial institution, the distribution of winnings is incorrect. Etc. can be easily discovered. The purchased lottery ticket numbers may all be read with a barcode reader or the like, and sent from the event master totaling screen 143 to the participant as an attached file. In addition, you may enable it to perform distribution of the dividend when winning a lottery ticket using this system. For example, the event master totaling screen 143 is provided with a notification means from the event master to the investor, and the notification content at this time automatically includes a distribution of a proportion corresponding to the invested amount of the investor. Thereafter, the event master can exchange the winning method and the like with each investor while confirming the amount and the investor indicated in the notification contents.

  FIG. 14 is a diagram showing an event registration screen for collecting examination fees and a totaling screen thereof as variations of events. FIGS. 11 to 13 show an example in which an individual user becomes an event master and registers an event. However, in SNS, organizations such as companies and universities can be registered as users, so events hosted by organizations are registered. It is also possible. The event may be the organization's original business. For example, the event registration screen 104 shown in the figure is an example in which collection of an entrance fee for a university entrance examination is registered as an event of this system.

  On this screen, event information as shown in the figure is input, but the event detailed information clearly states that there is a privilege when paying an examination fee using this system. For event organizers (universities), using this system has the advantage of reducing examination fee collection and payment confirmation. In addition, the use of SNS has the advantage that it can contribute to increasing the level of publicity of the university at home and abroad. In addition, for students and their parents, rather than paying from the university's website, etc., if they can pay with the SNS they normally use, they will have a sense of familiarity and deepen communication with friends on the SNS who will take the same university. You can also. Furthermore, there is a merit that an examinee who takes an entrance examination at several universities can use a unified payment method on the SNS instead of a separate payment method for each university. Moreover, since the financial institution will confirm payment, it is safe. It is attractive that you can easily pay the examination fee not only by bank transfer but also by credit card.

  The event master totaling screen 144 of the examination fee collection event may display the total number of examination fee payers using this system and a list of payment confirmation results for each financial institution. When the event master presses the “create a tabulation” button on this screen, for example, tabulation for each financial institution or tabulation for each student's profile can be performed. In this way, a certain usage fee may be imposed on the organization from the SNS side or the financial institution side for an event related to the original business as the organization becomes the organizer.

(Effect of embodiment)
According to this system, SNS and financial institution systems can be linked so that users can organize events and organize operations from the SNS that they normally use. In particular, collection of event participation fees, payment confirmation, settlement, etc. Can be made more efficient. In particular, the official symbol (paid mark), which is a payment confirmation of financial institutions (banks and credit card companies), is displayed on the event master's event top screen, so that the participants have certainly paid the participation fee etc. It can also be confirmed on SNS with the approval of financial institutions. In addition, the event ID, payment amount, payment destination, user ID on SNS, etc. are automatically transferred from the payment request notification received by the participant to the Internet site of the financial institution. Becomes easier. In addition, if this system is used, payment information will be aggregated, so accounting reports such as secretaries will be easier. Events handled by this system can include not only banquets and meetings but also donations, gifts of gifts, joint purchases of lotteries, and collection of fees for various events organized by companies and universities. So the range of use is wide.

  As mentioned above, although this invention was demonstrated using embodiment, it cannot be overemphasized that the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiments. Further, it is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention. In the above embodiment, the event participation fee payment system has been described using the present invention as a product invention. However, the present invention can also be understood as a method invention (event participation fee payment method).

1, 1A Event participation fee payment system 10 SNS system 11 Event master DB
11a Event information 11a1 Event master information 11a2 Event venue information 12 Event information synchronization part (SNS side)
13 Event registration part 14a Participant recruitment transmission part 14b Participant reception part 15 Participation fee payment request part 16 Payment information confirmation part 17 Payment information total part 20 Bank system 20A Credit card company system 21 Event slave DB
22 Event Information Synchronization Department (Financial institution side)
23 transfer acceptance unit 24 transfer processing unit 25 payment information transmission unit 26 member store information confirmation unit 27 authorization processing unit 31 event master terminal 32 participant terminal 33 event venue terminal 40 member store system 100 event registration screen 101 event registration screen (donation)
102 Event registration screen (congratulations)
103 Event registration screen (Lottery group purchase)
104 Event registration screen (test fee collection)
110, 111, 112 Event top screen 120 Transfer request screen (Payment request screen)
121 Card payment request screen (Payment request screen)
130 User Basic Information Screen 140, 141, 142, 143, 144, 145 Event Master Total Screen 200 Event Participant Recruitment Screen 210 Event Participation Fee Transfer Screen 211 Event Participation Fee Card Payment Screen

Claims (7)

An SNS system connected to a bank system and connected to an event master terminal of a user who is a user and an event organizer or secretary in a network, and a participant terminal that is a participant of the event,
An event registration unit that receives the event information from the event master terminal and registers the event information in the event information storage unit;
When the event is registered, a participant recruitment transmission unit that sends a notification to recruit participants of the event to the participant terminal;
From the participant terminal that has received the notification of the recruitment, a participant reception unit that receives participants of the event,
When the participant has selected bank transfer as the payment method for the participation fee of the event, a participation fee payment request unit that transmits a transfer request to the participant terminal,
A payment information confirmation unit that receives a payment notification indicating that the participant has made a transfer based on the transfer request from the bank system together with the official symbol of the bank, and transmits the payment notification to the event master terminal; An SNS system comprising: A bank system that is connected to an event master terminal of a user who is a user and an event organizer or secretary in a network and a participant terminal that is a participant of the event, and cooperates with an SNS system,
A transfer acceptance unit that accepts a transfer based on a transfer request transmitted from the participation fee payment request unit of the SNS system;
A transfer processing unit for executing the transfer;
A bank information system comprising: a payment information transmission unit that transmits the payment information of the participant together with the official symbol of the bank to the payment information confirmation unit of the SNS system after execution of the transfer. An SNS system connected to a credit card company system connected to an event master terminal of a user who is a user and event organizer or secretary, and a participant terminal that is a participant of the event in a network,
An event registration unit that receives the event information from the event master terminal and registers the event information in the event information storage unit;
When the event is registered, a participant recruitment transmission unit that sends a notification to recruit participants of the event to the participant terminal;
From the participant terminal that has received the notification of the recruitment, a participant reception unit that receives participants of the event,
When the participant has selected a credit card as a payment method for the participation fee of the event, a participation fee payment request unit that transmits a card settlement request to the participant terminal,
A payment notice indicating that the participant has made a payment based on the card payment request is received from the credit card company system together with the official symbol of the credit card company, and the payment notice is transmitted to the event master terminal. An SNS system comprising: a payment information confirmation unit. A system of a credit card company that is connected to an event master terminal of a user who is a user and an event organizer or secretary in a network and a participant terminal that is a participant of the event and cooperates with an SNS system,
A member store information confirmation unit for confirming that the business operator of the event venue is a credit card member store;
An authorization processing unit that receives a request from the member store information confirmation unit and approves the use of the credit card;
A payment information transmission unit for transmitting the payment information of the participant to the payment information confirmation unit of the SNS system together with the official symbol of the credit card company after approval of the use of the credit card;
A credit card company system characterized by comprising:   The participation fee payment requesting unit includes a participation fee payment request including an ID of the event, a user ID of the SNS system of the participant, and link information to an Internet site of a financial institution designated by the participant. The SNS system according to claim 1, wherein the SNS system is transmitted to a terminal.   The SNS system according to claim 1, further comprising a payment information totaling unit that totals payment information for accounting reports after the event ends.   7. The event according to any one of claims 1 to 6, wherein the event includes a banquet, a meeting, a solicitation for donations, a gift of congratulations, a joint purchase of a lottery ticket, and a fee collection for an event organized by an organization. The described system.