Patent Publication Number: US-2022222626-A1

Title: Social-referral network methods and apparatus

Description:
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 
     BACKGROUND 
     Field 
     Embodiments relate to social networks and, more particularly but not exclusively, to social network member generation and member connection tools. Embodiments also relate to social network user information database generation and searching tools. 
     Description of Related Art 
     Social networks of many kinds have been created on the Internet and have emerged to become among the most popular destinations on the World Wide Web (WWW). Social networks operate across country borders; the users may be in any geographic location which provides enormous opportunities to expand such networks to include many thousands, millions or even billions of users worldwide. However, retaining users in the social network as well as expanding the network to include new users can be challenging even for some of the most established social networks. 
     There is a need to provide improved apparatus and methods for expanding social networks. 
     SUMMARY 
     According to one aspect, there is provided, a computer implemented method for expanding membership in an online referral social network. The method can comprise receiving, by the online referral social network from a user over a computer network, at least one communication for registering the user in the online social referral network; confirming, by said online referral social network, a particular online referral social network member indicated in said at least one communication as having referred the user to the online referral social network is a member of said online referral social network; registering, by said online referral social network, said user as a new member in the online referral social network; determining, by said online referral social network, a referral commission; and paying, by said online referral social network, a referral commission to at least the particular identified referring member. 
     By paying a commission to a referring member of the online referral social network identified in the communication for registering the user, personal, non-commercial use members of the social network that would otherwise not be motivated to refer users to the social network are incentivized to do so and thereby cause further expansion of the social network. 
     According to another aspect, there is provided herein a database management system configured to return all referrals between members from a single database call, as well as to calculate a total amount of commissions payable from a single database call. 
     According to another aspect, there is provided a method for an online referral social network. The method can comprise for each one of plurality of members in a referral social network: determining from referral information of the online referral social network a combined number of referrals downline and/or upline from a member; and storing in a one call database, the combined number of referrals downline and/or upline from the member and the identity of the member; receiving a request to determine a commission payable to at least a referring member; in response to receiving the request, obtaining in a single database call from the one call database, the combined number of referrals upline and/or downline from the referring member; and determining a commission payable to at least the referring member utilizing said obtained combined number of referrals. 
     According to yet another aspect, there is provided an apparatus for expanding membership in an online referral social network. The apparatus can comprise one or more processors operably connectable to at plurality of user devices; a data bus coupled to said processor(s); a computer-usable medium embodying computer program code, said computer-usable medium being coupled to said data bus; and said computer program code comprising instructions executable by said processor and configured for performing one or more of the methods of the aforementioned aspects. 
     According to yet another aspect, there is provided a computer-readable medium including contents that are configured to cause a computing system to expand membership of an online referral social network by performing one or more of the aforementioned method aspects. 
     According to yet another aspect, there is provided herein an online referral social network website in which members are incentivized to refer other individuals to join the referral social network. Members build their social network by establishing contacts with other members, and build a database reflecting their contacts and referred members (“referrals”). Members can build their network based on categories of interest etc. to help them connect to others with similar interests. Keyword searching can be used to find out what users show preference for, such as movies, music, games, computers, software, sports, hobbies, travel, food, or social causes such as politics, environmental issues, and the like. According to embodiments, a user can enter a search term and be able to connect with other people who have indicated in a social network profile the search term or related terms as their own interest. Referral relationships between members are described herein as being either “upline” or “downline.” A member who refers another member to the referral social network is upline to the referred member, and the member referred by the upline member is downline of the upline member. By chaining together referrals in multiple iterations, for example an upline member is associated with a downline member who also is upline to yet another member, continuing for a desired number of associations in a vertical chain, individual members&#39; referral lists can grow exponentially. Compensation for referral is a key aspect of the referral social network described herein, and is distributed based on successfully referring new members to the referral social network. As a member&#39;s network of contacts with other members within the referral social network grows, so does their earning potential as compensation is distributed in a vertical manner among a chain of referred members. 
     In other embodiments, multiple compensation distribution models are contemplated herein. The rate of compensation for the first level of downline referrals may be higher for the anchor referring member than the second level of downline referrals, but the compensation rates may also be equal, or, in an embodiment, increased as additional referral levels grow. Compensating members for new member referrals thus quickly populates the referral social network, and allows members to establish direct contact with other members. 
     In another aspect, a database structure and management method thereof is presented herein. As described herein, the database of the referral social network is maintained by a server in communication with multiple clients over a computer network, and maintains member profile information for individual members that are collected when a member joins the referral social network. Member profile information includes the member&#39;s identity, such as a screen name, and the identity (if any) of an upline member who referred the member. In an embodiment, compensation is offered to a referring member for identifying the upline member upon the new member joining and paying to be a full member of the referral social network. This incentive preserves the vertical chain among members. Member profile information also may include personal interests such as described above. Member profile information also may include other information a user wishes to include on his or her individual profile, such as personal interests, either chosen from a menu presented to the user during a sign-up process, or user-supplied. Besides personal interests, information describing the user also may be included, such as gender, age, geographical location, what sort of housing the member resides within, resume items such as work history, education, family relationships such as number and ages of children, marital status, and the like. Group membership, political beliefs, religious beliefs, social issues of interest to a member, and the like, may also be listed in a member profile. Items possessed by the member, or simply items that interest the member (for example a ‘want” list), may also be listed on the member&#39;s profile. For example, a member may list automobiles, motorcycles, bicycles, consumer electronics, durable goods such as appliances, sporting goods, musical instruments, and the like, also may be included on a member profile. Member profile information can also include referral information associated with the individual member. For example, the member profile information may include referral relationships specific to individual members, identifying them within referral chains as upline or downline, the level within a referral chain where the member is placed, how many referral chains include the member, a current amount of compensation from referrals that is accrued by the member, a compensation target provided by the member or a group to which a member belongs, and a member&#39;s individual progress toward the target. 
     The database of the referral social network organizes the member profile information in searchable fields categorizing the individual membership items described above. This allows keyword searching to identify members to a searching member based on common interests, which facilitates establishing personal contacts. The database also stores referral relationships specific to individual members, identifying them within referral chains as upline or downline, the level within a referral chain where the member is placed, how many referral chains include the member, a current amount of compensation from referrals that is accrued by the member, a compensation target provided by the member or a group to which a member belongs, and a member&#39;s individual progress toward the target. 
     Many other features and advantages of the present invention will become apparent to one skilled in the art upon reading the following detailed description, when considered in conjunction with the drawings. 
    
    
     
       DESCRIPTION OF THE DRAWINGS 
         FIG. 1  illustrates a generalized block diagram of an embodiment of a referral social network system provided by a social network in which the system maintains member referral and commission tools and enables social network members to be compensated for referring new members to the social network; 
         FIG. 2  illustrates in block diagram form a network of user devices and server devices and equipment for implementing an online referral social network of  FIG. 1  according to one embodiment; 
         FIG. 3  illustrates major software modules utilized to administer an online referral social network application of the social network system of  FIG. 1  according to one embodiment. 
         FIG. 4  illustrates an exemplary member profile generated by the referral social network system of  FIG. 1  according to one embodiment; 
         FIG. 5  illustrates an exemplary user interface generated by the referral social network system of  FIG. 1  according to one embodiment; 
         FIG. 6  illustrates an exemplary org chart for representing referral relationships between members of the referral social network system according to one embodiment; 
         FIGS. 7-14  illustrate exemplary data structures for use within databases utilized in an online referral social network; 
         FIG. 15  illustrates a method for expanding membership of the referral social network system of  FIG. 1  according to one embodiment; 
         FIGS. 16 &amp; 17  illustrate a method for expanding membership of the referral social network system of  FIG. 1  according to one embodiment; 
         FIG. 18  is an exemplary user interface screen showing a login screen linking an external social network account to the referral social network according to one embodiment; 
         FIG. 19  is an exemplary user interface screen showing an income calculator to incentivize prospective members to join the referral social network according to one embodiment; 
         FIG. 20  is an exemplary user interface screen showing an information gathering tool that presents other individuals with whom a prospective or new member may establish contact and begin engaging in referral processes based on keyword searches; 
         FIG. 21  illustrates in flow chart form a method of determining referral commissions based on upline referrals according to one embodiment; 
         FIG. 22  illustrates an exemplary referral social network upline database table of a one call database according to one embodiment; 
         FIG. 23  illustrates in flow chart form a method of determining referral commissions based on downline referrals according to one embodiment; 
         FIG. 24  illustrates an exemplary referral social network downline database table of a one call database according to one embodiment; 
         FIG. 25  illustrates in flow chart form acts performed to install the software application of an embodiment of an online referral social network; 
         FIG. 26  illustrates in flow chart form acts performed to identify prospective users and sign them up in an online referral social network; 
         FIG. 27  illustrates in flow chart form acts performed for prebuilding subscribers in an online referral social network; 
         FIG. 28  illustrates in flow chart form acts performed for implementing a join process in which new members join an online referral social network; 
         FIG. 29  illustrates in flow chart form acts performed for a database population process; 
         FIG. 30  illustrates in flow chart form acts performed for an alternative database population process; 
         FIG. 31  illustrates in flow chart form acts performed for a process to create a recommended referring members list; 
         FIG. 32  illustrates in flow chart form acts performed for a process for displaying commissions details and requesting payment of commissions; 
         FIG. 33  illustrates in flow chart form a process for automatic commissions; 
         FIG. 34  illustrates in flow chart form an alternative commission payout process for paying members; 
         FIG. 35  illustrates in flow chart form a process for following referring members setup; 
         FIG. 36  illustrates a process for determining contents to display upon login; 
         FIG. 37  illustrates in flow chart form a process for a referring members rating process; and 
         FIG. 38  illustrates in flow chart form a members promoting and advertising process. 
     
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular embodiments, procedures, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. 
     Files, as referred to herein, generally are digital assets such as documents, emails, photographs, videos, audio files, and the like, which are capable of being stored digitally and reproduced on remote devices when disseminated across a computer network. 
     User devices, as referred to herein, generally are computing devices that communicate with a data processor, such as a server, across a computer network. User devices may be client devices such as any computing device capable of receiving and sending file sharing information over an electronic network. Such user devices may include personal computers, multiprocessor systems, microprocessor-based or programmable consumer electronics. Examples include desktop computers, laptop computers, tabular computers, notebook computers, cell phones, smart phones, display pagers, handheld or other wearable devices and the like. User devices may be web-enabled client devices that can communicate over the web and include a browser application that is configured to receive and transmit web pages, web messages and other web information. The browser application may be configured to send, receive and display text, graphics, and multimedia by means of a network protocol such as but not limited to Hypertext Transfer Protocol (HTTP) and/or wireless application protocol (WAP). 
     Unless otherwise stated, users, as referred to herein, means personal individuals that are typically consumers of goods and services and neither suppliers of goods and services nor service providers of the social network system. 
     Specific reference to components, process steps, and other elements are not intended to be limiting. Further, it is understood that like parts bear the same reference numerals, when referring to alternate figures. It will be further noted that the figures are schematic and provided for guidance to the skilled reader and are not necessarily drawn to scale. Rather, the various drawing scales, aspect ratios, and numbers of components shown in the figures may be purposely distorted to make certain features or relationships easier to understand. 
     Reference will now be made to the drawings in which the various elements of embodiments will be given numerical designations and in which embodiments will be discussed so as to enable one skilled in the art to make and use the invention. 
       FIG. 1  illustrates a generalized block diagram of an embodiment of a referral social network system provided by a social network that maintains referral and commission tools for expanding membership of the referral social network. Online referral social network computer system  1  is configured to incentivize personal members of the referral social network to refer other individuals to become members by offering to pay a referral commission to a referring member for causing others to join the social network. Personal, non-commercial members of the referral social network can monetize their own personal referrals and, in doing so, expand membership of the referral social network. The system includes a server or other processor system  10 , a referral social network software application  4  and one or more databases or other data storage or memory devices  3 . Referral social network application  4  is configured to enable a user to interact, via a user device  32 , with the referral social network system and is for example accessible to the user device by means of a browser  33  or other module. The databases  3  store member accounts and profiles, referral relationships and commission models. 
     The social network has a plurality of personal member accounts and one or more administrator accounts. The personal member accounts are characterized as individual user accounts, rather than an owner-operator account of the referral social network. Personal member accounts maintain personal profiles of the users (as referred to herein as member profiles unless otherwise stated) on the referral social network. The administrator accounts are accounts for owner-operators or others that have been given owner-operator access. 
     Online referral social network computer system  1  can be implemented in a variety of different network environments. One non-limiting example of specific internet network implementation of the referral social network system  1  of  FIG. 1  is shown in detail in  FIG. 2 . Server system  10  refers broadly to configurations of equipment that, as a system, function to collect data from users and to distribute information to users. In an embodiment, server system  10  may include multiple servers, each of which has functionality that is well-known by those skilled in the art. For example, servers  12 ,  13 ,  14  and  15  are servers having memories, processors, communication interfaces and the like, operating as server system  10 . Server  12  is a streaming media server. Database server  13  is a database server that manages databases  16 - 31 . In an embodiment, database server  13  manages a centralized database system organized as separate databases having specialized functions. Database server  13  is also contemplated as encompassing a broad, encompassing database system, which may be centralized as described above or a distributed database system. While these components are drawn as separate databases, it is to be understood that they be either separate database systems, or simply discrete data views constructed within a single database system. As shown, database server  13  may include user database  16 , platforms database  17 , upline database  18 , downline database  19 , subscriptions database  20 , referral database  21 , referring members database  22 , advertising database  23 , commissions database  24 , payments database  25 , secondary commissions database  26 , gaming database  27 , autopay database  28 , eCommerce database  29  and social metrics database  30 . In an embodiment, database  31  implements servers  16 - 28  as a single database, wherein the views are generated and stored as would be present on separate database systems  16 - 30 . 
     Web server  14  is a web server that controls communication with user devices and equipment  11  over Internet  41 . eCommerce Server  15  is an eCommerce server that handles financial transactions between parties, such as described here with customers for server system  10 . eCommerce server  15  is, in an embodiment, essentially an accounting server, which handles business transactions and payment transactions. eCommerce server  15  utilizes eCommerce database  29  for storage of related data and performing searching functions to provide financial analysis to users. User devices and equipment  11  are shown in various configurations in  FIG. 2 , and while lines are drawn between user devices  32 , it is to be understood that there is no requirement of direct, physical links between server system  10  and user devices  32 . Typically, communication between server system  10  and user devices  32  is implemented over a computer network utilizing a telecommunications network, such as a public telephone network, in communication with portable devices such as cell phones, smart phones, tablet computers, notebook computers, and the like. Thus, users can be located at geographically diverse locations, such as different cities, states, and countries around the world. In embodiments, browser program  33  is included in the memory and storage of a user device to provide a user interface between the user and internet  11 . Also as shown, user devices  32  can be a large number of devices, indicated by user device  32 N. As shown, server system  10  and user devices  32  are associated in a traditional client-server relationship. Server system  10  acts as a coordinator of files received from and distributed to user devices  32  that are operated by individual users who form an exclusive group that embodies a social network. These users are referred to herein as members, and are characterized as individuals who maintain personal profiles of themselves referred to herein as member profiles. Other users are referred to herein as commercial users, who use the online referral network to promote/recommend or advertise products and/or services to users referred to herein as members. User devices  32  may utilize browser  33  to serve as a user interface between the user and various webpages and visual displays. For commercial users, user devices can be computers such as desktop, laptop, workstation or server configurations operated by other entities, such as operating at well-known commercial websites, or simply access points providing Internet connectivity to other user devices. Such websites may be implemented on Facebook server  34 , Twitter server  36 , LinkedIn server  38 , and other social network server  40 . 
     Referring in more detail to the online referral social network system  1  of  FIG. 1 , the system has a software system including referral online social network application module  4  which can be stored in system storage/memory for execution by one or more processors to perform the methods for expanding membership and other methods of the embodiments described herein. The software system can include a kernel or operating system and a shell or interface. One or more application programs or modules, such as the social network application module  4 , may be “loaded” (i.e. transferred from storage into memory for execution by the processor). The system receives user commands and data through user interface; these inputs may then be acted upon by the processor, in accordance with instructions from operating module and/or application module. 
     One or more processors executing the referral social network application module  4  can in one non-limiting example be a network server site connectable within a network which is the Internet, but equally can be any one of, combination of, or interconnection of, but not restricted to: a local area network (LAN); a wide area network (WAN): a home network; and a wireless network. 
     Note that the term “module” as used herein may refer to a collection of routines and data structures that perform a particular task or implements a particular abstract data type. Modules may be composed of two parts: 1) an interface that lists the constants, data types, variable, and routines that can be accessed by other modules or routines and 2) an implementation that is typically private, accessible only to that module, and includes source code that actually implements the routines in the module. The term “module” may also simply refer to an application, such as a computer program design, to assist in the performance of a specific task. In other examples, at least part of the modules may be implemented by hard-wired logic or other circuitry. 
     Referring in more detail to the referral social network application  4 ,  FIG. 3 , depicts the general major functional modules  50  according to one embodiment that make up the logical structure of the referral social network application software  4 . Modules  50  are a user interface manager  55 , referring &amp; join up manager  54 , user profile manager  53 , database manager  52 , commission manager  56 , search manager  57 , referral organizer  58  and external social network interfacing manager  59 . User interface manager  55  is configured to generate and provide various graphical user interfaces of the referral social network for viewing and manipulation by a user on user devices  32 . Referring and join up manager  54  is configured to manage join up invites and join up requests. User profile manager  53  is configured to manage user profiles of existing members of the referral social network and of prospective members joining up to the social network. Database manager  52  is configured to manage storing and access of referral social network data stored in the databases  3 . Commission manager  56  is configured to manage commission calculation and payment processes to and from members. Referral Organizer  59  is configured to determine and organize referral relationships between users. External social network interfacing manager is configured to manage interfacing between the referral social network application  4  and software applications of one or more other external social networks. 
     Other modules (not shown) may be included in software application  4  according to a particular network implementation. By way of non-limiting example, for the internet implementation of  FIG. 2 , software application  4  according to one embodiment includes a communications manager that manages web server  14  and a payments module that manages eCommerce server  15  and assists in handling payments to and from members of the referral social network implemented on server system  10 . A ratings module can also be provided that is invoked by users who wish to rate member profiles. 
     Referring now in more detail to user interface module  55  of modules  50  of  FIG. 3 , in one embodiment, this module is configured to generate a dashboard user interface that is accessible via the user device for enabling a user to interact with the online referral social network application software. The dashboard user interface allows the user to provide instructions via user device  32  to modules  50  to initiate varies processes such as sending referral links to prospective members, selecting and authorizing access to the member&#39;s external social networks, searching for prospective members according to keyword searches, viewing and manipulating user profiles, viewing commission calculation and payment processes and visualizing organization of referral relationships between users. 
     A non-limiting example of such as dashboard user interface for a member according to an embodiment is depicted in  FIG. 4 . In this example, dashboard user interface  80  is managed by user interface manager  55  and accessible by the member through user device  32 . Dashboad user interface  80  has a plurality of buttons or icons that are selectable on the user interface by the member to instruct the software application modules  50  to perform particular processes. By way of one non-limiting example, dashboard user interface  80  has the following user operable control buttons or icons for enabling the member to operate the software application modules  50 : referral link sender  98  for sending referral links to users identified as prospective members, profile editor  81  for managing and editing the user profile of the member&#39;s user profile, platform  82  for selecting a member&#39;s external social network account and authorizing access to user connections and information therein, upline viewer  83  for viewing referral relationships upline from the member, downline viewer  84  for viewing referral relationships downline from the member, payments  85  for viewing and controlling payments to the member, commissions  86  for viewing commissions paid and calculating commissions based on referral information, autopay  87  for setting up auto payments to the member, referrals  88  for viewing user profile information of particular members downline from the member, referred  89  for viewing user profile information of particular members upline, search  90  for initiating keyword search queries, advertising  91  for viewing advertising, rate members  92  for rating particular members in the social network, and advertiser/promoter  93  for advertising, promoting and recommending goods and services etc. A lower portion of dashboard is configured to show upline image  94 , member profile  95 , and downline image  96 . 
     Referring now in more detail to the lower portion of dashboard  80 , as outlined above, the lower portion shows upline image  94 , member profile  95 , and downline image  96  for the member operating the dashboard or for another member selected by the member operating the dashboard profile editor  81 . A member&#39;s upline image  94  indicates where within the online referral social network a member fits in with respect to other members who have referred the member to the social network, or, in the case of commercial users, to a product or service. An exemplary upline image  94  is an organizational chart referred herein as an “org chart” and an example of which is shown in  FIG. 6 . Similarly, downline image  96  indicates where within the online referral social network a member fits in with respect to other members referred by the member. Similarly, image  96  can be another organization chart. In other embodiments, the entire display of dashboard  80  can be dedicated for these items, as would be useful for quickly viewing a plurality of member profiles as would be returned upon executing a database search based on keywords or other search criteria (surfing mode). 
     In an embodiment, volume indicators  97 A  97 B can be included in the dashboard for example as shown in the lower section of dashboard  80  of  FIG. 4 , to show quickly the size of the member&#39;s upline personal referral network or downline personal referral network, which are depicted as upline image  94  or downline image  96 , respectively. Volume indicators can be simple bar graphs displayed vertically, with a smaller volume shown as volume indicator  97 A, indicating that upline image  94  is a small network of personal contacts Volume indicator  97 B is configured to show a higher mark, indicating that the member&#39;s downline personal referral network is a larger number of members than make up the member&#39;s upline personal referral network. 
     An exemplary member profile of the referral social network system  1  according to one embodiment is shown in  FIG. 5 . Member profile  70  may be for example shown in dashboard  80  in full or collapsed view or accessible via the dashboard. Included in member profile  70  is information describing an individual member of the referral social network implemented on server system  10 . Information gathered during a member&#39;s signup process includes items such as name, location, age, memberships, and similar information for social networks, but also a categories of personal interest section  72 , which may include one or more topics of interest selected by the member, such for example upon signup. Member profile  70  can also include upline image  74  and downline image  76  showing referral relationships for the specific member associated with the user profile. 
     Search parameters may be included in the user profile with selections of categories of personal interest  72 , such as age, location, gender, memberships, number of followers, number of referrals, number of times the member has successfully been referred, or other suitable information contained within a member profile  70  or elsewhere. 
     Reference will now be made in more detail to upline and downline images for example as shown in dashboard  80  and user profile  70 . Upline image  74 , 94  show an upline chain of referrers beginning with the member who referred the member to the online referral social network, if one exists, and, in an embodiment, continues for example vertically from the member who referred the member to his or her referral, on up to a predetermined or desired number of levels. In an embodiment where the member is one of a plurality of referred members by another member, upline image can be a tree structure showing relationships between members of the online referral social network. Downline image  76 ,  96  is an image of a chain of downline referrals for a desired number of levels. In an embodiment where a member has referred multiple members, the downline image  76 ,  96  can be tree structure of the downline relationships between the member and subsequent referred members can be displayed to the member. Profile  95  shows the member profile information for the member accessing the dashboard  80 . 
     Upline image  74 ,  94  are beneficial for use in rating the quality of referrals through a rating process, where members can rate members of their personal contact list shown in whose referrals have been relied upon by the member, and thus the member can rate the experience either by number, expressing a like or dislike, or generating a written commentary, or selecting expressive icons that convey a member&#39;s feeling, good or bad, about the referral. 
       FIG. 6  illustrates an exemplary org chart  99 , which shows relationships between individual members who have member profiles on the online referral social network. An org chart  99  showing upline referrals is one way to show upline image  74 , 94 . An org chart  99  showing downline referrals is one way to show downline image  76 , 94 . For example, on  FIG. 6 , this is shown where member m 1  is located in relation to m 4 . The number of relationships separating one member and another can have degrees of separation beyond a simple direct relation. 
     Referral chains, such as Org charts  99  or other organization structures as referred to in the above methods can be generated from data base records of the social network system  1 . In one embodiment, exemplary database records for an implementation of org chart  99  having number of members n in either an upline or downline relationship, records  1000  include a first field  1102 , a second field  1104 , and a null field  1106  as shown in  FIG. 7 . As an example, this organization can indicate a referral relationship. For example, member  1 , in field  1102 , is the referrer of member  2  in field  1104 . In the next record, member  2  is the referrer of member n−1. In the final record, there is only member n, who has yet to refer anyone. This record reflects this status by placing a null value in field  1104 . Org chart  99  can be constructed from records  1100  by traversing records  1000 , beginning at the bottom, where the null value is detected in field  1104 , and placing member n at the bottom of org chart  99 , and working upward to construct a tree such as shown in org chart  99 . For members having referred multiple members, record  1100 , shown in  FIG. 8 , illustrates field  1112  as the referrer, and multiple members in fields  1114 . By traversing record  1100 , this list of multiple-referring members can be constructed in the tree relationship shown in org chart  99 . It is to be understood that the same organization shown in records  1100 ,  1110  can be applied to other databases in server system  10 . Similarly, multiple platforms from which users are allowed to log in to server system  10 , such as external social network platforms  34 - 40  shown in  FIG. 2 , can be supported in platforms database  22  by storing specific platform configurations in record  1130  ( FIG. 9 ), each individual external platform supported by server system  10  can be identified in field  1132  and associated with its specific configuration information in field  1134 . 
     Other records of the system  1  may for example include records of advertisers. Advertisers can also be organized as shown in the database of  FIG. 10  in record  1140 , with advertisers identified in field  1142  and associated with their individual advertisement or other information in field  1144 . Payments for members can be implemented through record  1150  ( FIG. 11 ), with members identified in field  1152 , payments disbursed to members in field  1154 , and payments received from members in field  1155 . Record  1150  can be used for other users of server system  10  as well as members, such as advertisers or commercial users. Autopay referral compensation amounts for referring members can be implemented by record  1156  shown in  FIG. 12 , having field  1158  to identify the member and field  1160  to show the autopay amount requested by the member. Commissions earned by members for referring new members can stored in record  1162  in  FIG. 13  in fields  1164  identifying members and fields  1166  identifying corresponding amounts. 
     Gaming points, or another secondary commission or bonus paid to members, can likewise be organized in record  168  ( FIG. 14 ) for individual members identified in field  170  and associated with a points value in field  172 . The records shown in  FIGS. 7-14  are to be considered as illustrative and not exhaustive; other records are discussed below and can be similarly illustrated. 
     A method for expanding membership of an online referral social network according to one embodiment implemented in the social referral network system  1  will now be described with reference to  FIG. 15 . As indicated in the flow chart illustrating method  100 , the online referral social network system  1  receives over a computer network from a user device one more communications for registering a user as a member in the online social referral network (process  101 ). The system  1  then confirms a particular online referral social network member indicated in the communication as having referred the user to the online referral social network is a member of the online referral social network (process  102 ). The system registers the user as a new member of the online referral social network (process  103 ). A referral commission payable to the referring member is then determined (process  104 ). The system then initiates payment of the referral commission over the computer network to the identified referring member (process  105 ). 
     By the online referral social network system determining from one or more communications for registering a user that a referring user identified in the communication is a referral social network member determining and paying a referral commission to the referring member automatically, personal, non-commercial members of the referral social network can easily monetize their own personal referrals and, in doing so, expand membership of the referral social network. The method incentivizes personal members to refer other individuals to become members thereby accelerating expansion of the membership of the referral social network. 
     In one embodiment, method  100  is implemented by modules  50  of software application  4 . For example, process  101  is implemented by user interface manager  55  receiving and handling one or more communications. The communication(s) can be any communication received over the computer network containing information for registering the user as a member in the online referral social network and containing the identity of the referring member. In one example, the identity of the referring member can be contained in the same communication as a join up request communication. In another example, the identity of the referring member can be contained in a separate communication from the join up request communication. Such communications can be any type of electronic communication received from a user device  32  over the computer network. For example, such communications can be e-mail communications or communications resulting from web activated links that are generated either outside or within the online referral social network environment. 
     For example, process  102  is implemented by user profile manager  53  accessing member profile information and the referring and join manager module  54  comparing the referring member identity contained in the communication, or a future communication for example received as part of the subsequent registration process, with member identities contained in the member profile information. If a match between the referring member identity contained in the communication and a member identify in a member profile is found, the join up manager  54  confirms that the referring member identified is an online referral social network member. If a match is not found, the join up manager sends a communication to the user device of the user alerting the user an error in confirming the referring member and requesting that the prospective member re-confirm the referring member&#39;s details. 
     For example, process  103  is implemented by the join up manager  55  registering the user as a new member in the referral social network system. For example, process  104  is implemented by commission manager  56  calculating a referral commission which can be for example be based on the referring member referral information stored in the referring members user profile or elsewhere. In one example, the commission manager  56  determines the commission to be paid to the referring member according to a referral chain associated with the referring member. For example, the commission can be determined according to the number of referrals the referring member has already made. In yet another embodiment, commission manager  56  also pays a commission associated with the referral made by the referring member to other members that already have a referral relationship with the referring member. 
     For example, commission manager  56  implements process  104  by managing electronic payment of the referral commission to the user. Commission manager  56  can pay the referring member and any other members electronically in different ways. For example, commission manager  56  can instruct an ecommerce server to initiate a funds transfer online from a bank account associated with the online referral social network to the bank account of the identified referring member. 
     In one embodiment, members or prospective members of the online referral social network are personal individuals, non-commercial use members that have personal, non-commercial use accounts and profiles. These members are neither commercial users, such as suppliers of goods and services, nor are they social network service provider members. In one example, these individuals may be consumers of goods and services and not suppliers of goods and services. The system can determine the identify of the referring member by looking up information in personal non-commercial user profiles of these members according to information in the inquiry or join request received from the user device. In another example, these members are commercial users with commercial user profiles. In yet another example, these members are made up of a combination of both the personal individual members and commercial user members. 
     In one embodiment, users are either registered members (member user or member or referring member) or unregistered guest users (guest or a guest user). Members generally have more access to content, premium content and functionality than Guest Users. Registered Users have ‘registered’ by providing identification information such as: valid email address, a username and other identifying information. Registered users are either non-paying affiliates (affiliate or Referring Affiliate) or they are a paying member by virtue of making a one-time or by making payments in a recurring subscription. 
     A method for expanding membership of an online referral social network according to another embodiment implemented in the social referral network system  1  will now be described with reference to  FIG. 16 . In this particular example, it is assumed that a user has been referred to the referral social network by a referring member of the referral social network and that the user wishes to join. As indicated in the flow chart  110 , referral social network system  1  initially presents over the computer network to a user device a login interface for the user to log on to the system from the user&#39;s external social network for the purpose of setting up registration to the referral social network (process  111 ). Process  111  can be implemented by external social network interfacing manager  59  of software application  4 . The user can login using different types of information such as the user&#39;s name and/or e-mail address. 
     Online referral social network system  1  receives authorization over the computer network from the user device of the user for the online referral social network system to access over the computer network and use the user&#39;s external social network account and user personal info, name, gender and age (process  112 ). Process  112  can for example be implemented by external social network interfacing manager  59 . Such authorization to use the user&#39;s external social network account information can be implemented in different ways. For example, such authorization can be given by a user clicking on an icon. Authorization to use the user&#39;s external social network account can for example include authorization to access the user&#39;s external social network followers/connections information, access password and messages. The referral social network can use the user&#39;s external social network account information in different ways. For example, the referral social network can read posts, messages, timeline information etc. in the user&#39;s external social network account, see who the user is following or connected to in the external social network, update the user profile in the external social network account and/or post to or send messages from the external social network account. 
     In another embodiment, the system can present the initial login interface for the user to login directly into the referral social network system rather than from their external social network and then once the user has logged in directly to the referral social network present the login interface for logging in to the external social network user. Logging in to the external social network may then automatically authorize the system to use the user&#39;s external social network account. One non-limiting example of a login interface for authorizing the system to use the user&#39;s external social network account information is depicted in a screen shot  130  of  FIG. 18 . 
     By providing such login interfaces, the user of the system is able retrieve information including follower/connection information from separate systems using one interface for making subsequent referrals. Many contacts and connections may now be completed electronically, which reduces redundant data entry and mistakes made by multiple manual inputs. 
     Method  110  continues as shown in  FIG. 16  by presenting an income calculator interface to the user device of the user for determining potential commission earnable according to number of referrals sourced from the user (process  113 ). The income calculator interface receives user instructions from the user about the number of potential referrals the user can source, calculates a potential earnings and presents the calculated earnings on the calculator interface. By providing such a calculator for viewing and manipulating on the user device of the user, a user is incentivized to refer other users to the referral social network system. One non-limiting example of such an income calculator is shown in the screen shot  131  of  FIG. 19 . Exemplary Income calculator interface calculates potential earnings based on information such as the number of people the user can personally refer over the course of a particular length of time, such as 6 months, and the number of people each of those referrals can refer in that length of time. 
     As indicated in  FIG. 16 , method  110  continues by the system  1  receiving user registration information over the computer network from the user device (process  114 ). Process  114  may be for example implemented by referring and join up manager  54  in conjunction with user interface module  55  and other modules of the software application  4 . In one example, system  1  generates an enrollment form for presenting to the user device and completing by the user. Registration information received by the system  1  can include for example name, e-mail address, user name, password, gender, birthday, affiliate referrer identification, confirmation that the user is human and agreement to terms of service. In one example, receiving user registration process  114  info can include receiving a signup validation link activation communication in response to sending a signup validation link to the e-mail address of the user and the user clicking on the link to validate the identity of the user. 
     Method  110  continues by system  1  registering the user as a new member of the referral social network (process  115 ). Process  115  may be implemented by join up manager  54  in conjunction with user interface manager  55  and profile manager  53 . The new member may be presented with a login interface for logging in as a member into the referral social network or may be automatically logged on via the signup validation process. 
     Method  110  continues by system  1  generating a member profile for the new member (process  116 ). The process  116  can be implemented by for example user manager  54  in conjunction with user interface manager  55  and other modules. In one embodiment, an interactive process is implemented during the join up process or shortly after registration is implemented in which user interface manager renders a user interface screen on the user device requesting user profile information, such as name, age, gender, location, etc. In one example, the generated user interface screen requests information relating to the referring process, such as how much income the user wishes to earn from the referral process, keywords describing personal interests of the member etc. One example of such a user information request interface screen is interface screen  132  shown in  FIG. 20 . As shown in the screen shot  132 , the user interface screen includes requests for “about me” information, i.e. information about the user; the user&#39;s referral earnings target; products or things the user wishes to buy or afford; importance of financial priorities; how much the user wishes to donate to a worthy cause, such as but not limited to a non-profit and/or awareness campaign or social campaign, the number of followers the user would like to procure, selection of personal referral categories such as auctions, blogging, education, gaming internet marketing, movies and theaters, online shopping, social network, voip, audio, books and magazines, group discounted coupons, mobile, online dating, restaurants, travel, video etc; selection of kind of groups, clubs, organizations of which the user is a member, user-selected keywords describing a user&#39;s personal interests, such as financial freedom; areas or topics that the user desires to have social impact and make the world a better place, profile pictures of the user. 
     Method  100  includes receiving a personal interest search query for generating a recommended following/referral list for assisting the user in following members in the referral social network (process  117 ). Process  117  can be implemented by search manager  57  in conjunction with other modules of application  4 . In one example, receiving the personal interest search query can include receiving keywords entered into the user information interface screen, such as user interface screen  132  of  FIG. 20 . In response to receiving the query, method  100  continues by the system searching among other member information for members having interests similar to queried personal interest (process  118 ). The system then generates information on other members identified from the search as having similar interests to the user (process  119 ) for following and/or referring to the referral social network by the member. One example of such a recommend following/referral list is depicted in the screen shot of  FIG. 20 . The recommend following/referral list can, for each member identified in the search, identify the member and include a follower link for linking the user to the external social network of the listed member and following them in their external social network. 
     By receiving such search queries and searching among other member&#39;s internally in their internal referral social network account, members can easily target and expand, either personally and/or electronically, such as via follower links, their personal and social networking contacts and connections through the system according to specific key word(s), key phrase(s) or key function(s) information. 
     Method  110  continues by system  1  receiving user request to follow one or more of the identified members, internally and/or externally via another social network, and/or to send over the computer network one or more goods/services referral links to the identified members (process  120 ). In one embodiment, process  120  can be implemented automatically without further interaction with system  1  by the member. The identified member(s) receive over the computer network the referral links on their user devices. The referral links can be sent to the users in different ways. In one example, the referral links can be sent to the e-mail addresses of the identified members. In another example, the referral links can be sent to the identified members other accounts in the external social network. The system incorporates an identifier in the referral links identifying the referring member. In one example, the identifier can be embedded and hidden from the user viewing the received referral link on their user device. In another example, the identifier can be included in the referral link and visible to the user viewing the received referral link. 
     The system can also receive registration requests over the computer network from user devices of prospective members that have been referred to the online referral social network by the new member for example by the new member sending a referral link to the prospective member (process  121 ). The request can be any type of electronic communication received from over the computer network from a user device. 
     Method  110  continues by system  1  confirming the referring member identified is an online referral social network member (process  122 ). The system can receive the name or identifier of the referring member during the registration process in different ways. For example, when a referral link sent by the system to the recipient includes the identifier of the referring member, the system can receive a referral ink activation message including the identifier and then compare this identifier to identifiers of members in the referral social network to determine if the referring member is a member of the referral social network. In another example, system  1  receives the name or other identifier entered by the recipient via a user interface page presented by the system  1  on the user device of the recipient during the registration process. One example of such an interface page is the enrollment form described with reference to the process  114  hereinbefore. 
     Method  110  then continues by system  1  determining the referral commission payable to the referring member (process  123 ). In one embodiment, the system  1  determines the commission to be paid to the referring member according to a referral chain associated with the referring member. For example, the commission can be determined according to the number of referrals the referring member has already made. In yet another embodiment, the system  1  determines the referral commission payable to other members that already have a referral relationship with the referring member so that a total referral commission can be distributed among the referring member and other members having a referral relationship with the referring member. In other embodiments, the commission can be determined according to one or more of the embodiments using a one call database as will be explained in more detail below. 
     Method  110  continues by the system paying the referral commission to at least the particular identified referring member (process  124 ). Commission manager can do this for example by obtaining payment details from the referring members profile and handling electronic payment of the calculated referral commission to the referring member&#39;s account. 
     In other embodiments, method  110  is not limited to the sequence of processes shown in  FIGS. 16 &amp; 17 . By way of example, receiving user registration info (process  114 ) and/or registering user as a new member (process  115 ) can be implemented before for example process  111 ,  112 , or  113  or later in method  110 . Presenting income calculator (process  113 ) can be omitted or implemented before process  111 ,  112  or  113  or later in method  110 . Processes  116 - 119  can for example be omitted. In other embodiments, processes of method  110  can be implemented by current members of the referral social network, where appropriate, as an alternative or in addition to new users in the registration process. For example, processes relating to accessing and authorizing use of external social network accounts (process  111  &amp;  112 ), receiving interest queries (process  117 ), searching for members (process  118 ), presenting members identified from searching (process  119 ) and other processes  120  to  124  can be implemented for current members wishing to receive further compensation by refer other users to register with the network. 
     As mentioned hereinbefore, the process of determining referral commissions in the methods for expanding membership according to embodiments can be performed in different ways. A method for determining referral commission based on referral relationships in the online referral social network according to one embodiment will now be described with reference to  FIG. 21  which is a flow chart outlining the method  160 . System  1  determines from a referral chain information a combined number of referrals upline from a particular member in the referral chain (process  161 ). Process  161  then repeats for each other member in the chain (process  162 ). For each member upline from the particular member, the system stores in a one call database the number of their referrals (process  163 ). One non-limiting example of such a one call upline database is represented in table format in  FIG. 22 . 
     In one embodiment, system  1  can implement processes  161  to  163  dynamically by incrementing the number of upline referrals for each member as a result of each new member being registered in the online referral social network (process  164 ) according for example to process  103  of method  100 . 
     System  1  then receives a request to determine referral commission for distribution among one or more members in a referral chain as a result of a particular member performing a referral (process  165 ). In one embodiment, system  1  receives a referral commission determination request which has been generated internally in response to the system registering a new member to the referral network according to for example process  103  of method  100 . In another embodiment, system  1  receives a referral commission determination request that has been generated externally for example by a user of a user device wishing to view referral commissions. System  1  then obtains in a single database call the total number of referrals associated with a particular member that is making a referral (process  166 ). System  1  can then determine a commission payable to the particular referring member (process  168 ) and, if desired, other members, according to the total number of referrals obtained for the particular member (process  167 , 168 ). The system can determine the commission payable according to different commission models. In the example of  FIG. 21 , system  1  determines the total referral commission (process  168 ). Determining the total referral commission can be achieved for example by looking up a pre-fixed commission in the system or setting the total referral commission according to the total number of referrals. 
     In one embodiment, system  1  can distribute referral commission among a particular member and other members in the referral chain. For example, for a particular member making a referral, system  1  can obtain in a single data base call the total referrals associated with the particular member, and then obtain in another single database call the total referrals for a member upline from the particular member in the referral chain, then repeat this process for each other member upline. System  1  can then retrieve the total upline referrals associated with each member upline from the particular member and then distribute the referral commission among the particular member and these upline members according to the distribution of total commissions of each of these members. 
     Referring in more detail to the one call database system utilized in process  166 , an exemplary upline database table of such a one call database system is shown in  FIG. 22 . This database table keeps record of the user_id of each member in the user&#39;s structured upline genealogy. With the structure of the Structured Upline Referrers Database table, it is possible that just one simple database call can retrieve the user_id of the member&#39;s Upline referrers up to “x” number of referrers. With this one call database, only the member&#39;s direct referrer is recorded which results in much longer access time to find all “x” number of Upline Referrers. So for example, to find the Mary&#39;s 100 th  Upline referrers, a database call would find
         Referrer_1 (user_id=41866)   then find Referrer_1&#39;s referrer (Referrer_2=40100) and   then find Referrer_2&#39;s referrer (Referrer_3=38311)   and so on until referrer_10 is found.
 
In the example above, the number of database calls is 100.
       

     As the one call database of  FIG. 22  scales up in size due to larger and larger number of users, this database table structure saves a tremendous overhead of database calls. The less database calls, the faster the web page request is served. 
     In the example of  FIG. 22 , the number of Upline referrers maintained in the table is “x”. In the current implementation, the actual number is 100. But there is no theoretical limit to “x”, simply a matter of practical size of the database, and it can be adjusted as the number of users of the invention increases over time. 
     Any time a user, such as Mary, makes a commissionable product purchase or buys advertising or services, the commission compensation is distributed amongst a configurable number of levels in the Upline database structure. 
     The upline database may store these relationships between individuals as a table, or as a simple linked list of pointers to storage locations or memory locations containing the relevant data for each entry in the list. 
     Whilst the embodiments described above with reference to method  160  and one call database table  FIG. 22  refer to upline referrals, in other embodiments of these methods and one call databases, referrals can be downline referrals or a combination of upline and downline referrals. Furthermore, in another embodiment, the method of obtaining combined referrals in a single database call can be utilized in processes other than determining referral commissions payable to members. For example, in one embodiment, the method of obtaining total referrals in a single database can be utilized for the purpose of generating user interface upline or downline images including referral numbers and alternatively or additional commissions earned. Such generated user interface upline and/or downline images can be for example included in a user interface dashboard such as dashboard  80 . 
     A method for determining referral commission based on referral relationships in the online referral social network according to another embodiment will now be described with reference to  FIG. 23  which is a flow chart outlining method  170 . System  1  determines the number of downline referrals for each member in a referral chain or other organizational structure (process  171 ). For each referral chain or other organizational level, the total number of referrals downline from members at the same level is stored in the one call database (process  172 ). Processes  171  &amp;  172  are repeated for each other level (process  173 ). System  1  receives a referral commission determination request (process  174 ). In one embodiment, system  1  receives a referral commission determination request which has been generated internally in response to the system registering a new member to the referral network according to for example process  103  of method  100 . In another embodiment, system  1  receives a referral commission determination request that has been generated externally for example by a user of a user device wishing to view referral commissions. System  1  then obtains in a single database call the total number of downline referrals for all members at a particular level in the referral chain (process  175 ). System  1  then determines a referral commission payable to the referring member and, if desired, other members downline, utilizing the combined number downline referrals for all members at a particular level in the referral chain (process  176 ). 
     Referring in more detail to a one call database system utilized in process  170 , an exemplary upline database table of such a one call database system is shown in  FIG. 24 . This database table keeps record of the number of subscribers in each of the organizational levels in the user&#39;s structured Downline genealogy. With the structure of the Structured Downline Subscribers Database table, it is possible that just one simple database call can retrieve the number of Downline subscribers a member has, up to “x” levels down. Without this one call database, only the total number of the user&#39;s personal referrals or subscribers is recorded. So for example, to find the total number of subscribers resulting from the user&#39;s 10 th  organizational level, these are the database calls to get that number: get total personal referrals (Level_1=10)
         1. for each of the 10 users found in step 1, get their total personal referrals. (10 database calls, Level_2=121)   2. for each of the 121 users found in step 2, get their total personal referrals. (121 database calls, Level_3=256)   3. for each of the 256 users found in step 3, get their total personal referrals. (256 database calls, Level_4=777)   4. for each of the 777 users found in step 4, get their total personal referrals. (777 database calls, Level_5=2012)   5. for each of the 2012 users found in step 5, get their total personal referrals.    (2012 database calls, Level_6=5150)   6. for each of the 5150 users found in step 6, get their total personal referrals.    (5150 database calls, Level_7=10261)   7. for each of the 10261 users found in step 7, get their total personal referrals.    (10261 database calls, Level_8=22767)   8. for each of the 22767 users found in step 8, get their total personal referrals.    (22767 database calls, Level_9=32904)   9. for each of the 32904 users found in step 9, get their total personal referrals.    (32904 database calls, Level_10=97279)   Total number of database calls without the invention: 74,258   Total number of database calls using the invention: 1
 
In the example in the above scenario without the one call database, the number of database calls grows exponentially and quickly becomes impractical.
       

     But with the one call database of embodiments, it only takes 1 database call to get that information. As the one call database scales up in size due to larger and larger number of users, this database table structure saves a tremendous overhead of database calls. The less database calls, the faster the web page request is served. 
     In this example, the number of Downline Subscriber Levels maintained in the table is “x”. In the current implementation, the actual number is 100. But there is no theoretical limit to “x”, simply a matter of practical size of the database, and it can be adjusted as the number of users of the invention increases over time. 
     A method of operating the dashboard user interface  80  of the social network for exploring referral relationships will now be described. In response to receiving a selection of the referrals viewer  88 , dashboard shows individual member profiles of members whom the member using dashboard  80  has successfully referred (i.e. profiles of the individual members of the chain of downline members shown on). Messaging functionality is included in this manager to allow a member to contact any of these members by clicking on their member profile and selecting message to open a live chat, send email, follow selected member and other suitable communication mechanisms. In response to receiving a selection of the referrals viewer  89 , dashboard shows specific individual member profiles of the member&#39;s upline tree (i.e. profiles of members who would be shown in the chain displayed by upline manager). Thus, while upline manager  83  and downline manager  84  can be utilized to show the member his or her upline tree and downline tree, respectively, referred manager  89  and referrals manager  88  show individual member profiles of members of the upline tree and downline tree, respectively. 
     Directing attention to  FIG. 25 , there is shown a process for installing the software application of the online referral social network according to one embodiment. Beginning at process  200 , the administrator copies files to the supported platform on which the referral social network runs. At process  202 , the administrator logs in to the supported platform, and, at process  204  a display is generated that prompts the administrator to supply administrative access credentials (updating containing a post snippet). At process  206 , access privilege data for the administrator is retrieved. Continuing to process  208 , the administrator selects “install plugin” from a displayed menu. A plugin installation process proceeds at process  210 . Continuing to decision process  212 , a determination is made as to whether or not the platform on which installation is to be performed is supported or not. If it is not a supported platform, control transitions to process  214 , where an error message is displayed, and the process terminates. Otherwise, in the case of a supported platform, control transitions to process  216 , where the administrator may customize configuration settings for the referral social network. At process  218 , configuration settings are saved to a database. At process  220 , an auto-test of the plugin installation and configuration is made, At decision process  222 , a determination is made as to whether or not the auto-test was successful, If not, control returns to process  214 , where an error message is displayed, and the process terminates. Otherwise, in the case of a successful auto-test, control transitions to process  224 , where a message is displayed to the administrator that the plugin was successfully installed, and the process terminates. 
     Directing attention to  FIG. 26 , a flow chart for a process for viewing prospects for the referral social network is illustrated. Beginning at process  230 , a prospective member to a supported social network logs in. At process  232 , the prospect timeline view, a prospective member sees and clicks on a referring member&#39;s timeline, displaying links to posts made by the referring member to the prospective member. System updates containing the posts snippet. At process  234 , the prospective user clicks on the post links, and is taken from the social network to the referring member&#39;s posts posted on the referring member&#39;s website to view the referring member&#39;s posts which are displayed to the prospective member at process  236 . In one example, this may be a website generated in the referral social network for the referring member such as a social campaign page. At decision process  238 , a determination is made as to whether or not the prospective member wants to use the social referral network to earn money. If no, control proceeds to decision process  240 , where a determination is made as to whether or not the prospective member wants to join the referral social network. If no, the process ends. If yes, the prospective member subscribes to the referral social network at process  242 , and the process ends. Returning to decision process  238 , if the prospective user chooses to make money, control proceeds to process  244 , where the prospective member views and interacts with a presentation about the referral social network (see for example interactive presentation described hereinbefore). At decision process  246 , a determination is made as to whether or not the prospective member wishes to purchase a membership to the referral social network. If yes, then the prospective member becomes a member through the join process, and the process ends. Returning to decision process  246 , if the prospective member chooses not to join, process ends. 
     Directing attention to  FIG. 27 , a flow chart for a process to prebuilding subscribers to the referral social network according to embodiment is shown. Beginning at process  260 , the prospective member logs in to a supported social network. At process  262 , in the prospective timeline view the prospective member is shown a link to the presentation of the referral social network. In this example, prospect sees and clicks on user&#39;s social referral network timeline and the system sends an update containing the link to the referral network presentation (eg. monetization presentation described above or a referring members socal campaign website generated in the referral social network). At process  264 , the prospect interface view leaves the supported social network and connects to the referral social network. At process  266 , the prospective member receives a presentation to the referral social network and/or other member&#39;s product or service, and, at decision process  268 , a determination is made as to whether the prospective member wants to watch the rest of the presentation. If no, the process ends. If yes, then at decision process  274 , a determination is made as to whether or not the prospective member wants to authenticate and connect to the referral social network using a supported social media account. If no, then control proceeds to process  276 , an email opt-in action, where the prospective user fills in his or her name and email address and submits them to the referral social network. At process  278 , the prospective member&#39;s information entered at process  276  is written to a leads database, and an email validation is sent to the prospective member at process  280 . At process  282 , the prospective member opens the email sent in process  280 , and clicks on a validation link contained in the email. At process  284 , the prospective member is directed back to the referral social network website and the presentation of referral social network and/or the other member&#39;s goods or service. Returning to decision process  274 , if the prospective member chose to authenticate by a social media account, the prospective member clicks on the social media service of their choice and allows the referral social network to access their account at process  286 . Control then proceeds to process  284 , described above. Continuing to process  288 , the prospective member validation is written to the leads database. At process  290 , the prospective member views the social referral network presentation and interacts with the presentation. At decision process  291 , a determination is made as to whether or not the prospective member wishes to purchase a membership to become a member. If no, the process ends. If yes, the prospective member joins at process  292  (see  FIG. 40 ). 
     Directing attention to  FIG. 28 , a flow chart for a join process for a prospective member according to one embodiment is shown. At process  300 , the prospective member, now referred to as a new user, fills in a join form. At decision process  302 , a determination is made as to whether or not the data provided at process  300  is valid. If not, control loops back to process  300 . Otherwise, control transitions to process  304 , where the new user fills in additional data, which is also verified at process  306 . At process  308 , email validation is sent to the new user. At process  310 , the new user&#39;s data is stored in user database  16 . At process  312 , the new user logs into his or her email account, opens the email sent at process  308 , and clicks on the validation link contained in the email. Control proceeds to process  314 , where the database process described below and illustrated in  FIGS. 29 and 30  is performed. At process  316 , an order and payment process is performed on behalf of the new user. At process  318 , commissions are paid to referring members, described below and illustrated in  FIG. 28 . At process  320 , social connections are set up, and relationships between members of the referral social network are recorded in referring member database  127 . At process  322 , the new user subscribes to the recommended list of referring members. At process  324 , the new user is presented with choices of adding friends to the social network, declaring himself or herself to be a fan, or follow the recommended list of social networking contacts. At decision process  326 , a determination is made as to whether or not the new user has a link to promote. If no, the process terminates. If yes, the new user&#39;s link is entered at process  328  for other users to follow. The process then terminates. 
     Directing attention to  FIG. 29 , a flow chart for a database population process is shown. At process  340 , the process transitions from process  314  of  FIG. 28 . At process  342 , pertinent user data is obtained from the new user by accessing a user database and displayed (process  344 ). At process  346 , database records are created for each of the supported platforms to prebuild the subscriber base. At process  348 , these database records are written to platforms database  17 . At process  350 , a downline referrals record is created to track the number of subscribers. At process  352 , this record is written to upline database  18 . At process  354 , the user&#39;s referrers upline record is displayed upon its retrieval from upline database  18  (process  356 ). At process  358 , the new user&#39;s upline record is set to identify a referring member (set user.upline[0]=referrer). At process  360 , upline records are assigned to indicate referring members (for every level “x” in the upline record set user.upline[x]=referrer.upline[x−1]. At process  362 , these assigned upline records are written to the downline database  18 . At process  364 , a control loop begins. For each upline referring member, the downline number for that member is incremented (process  366 )(increment the number of subscribers in the referrer&#39;s downline record corresponding to the current level by 1; referrer.downline[$x]+=1;$x+=1), and the number is written to the upline database  18  (process  368 ). Then, at decision process  370 , a determination is made as to whether or not the upline referring member is eligible to receive subscriptions. If no, a notice is sent to the upline referring member to indicate a missed subscriber at process  372 , and this indication is written to the subscriptions database  20  at process  374 . If yes, then the subscription is made for the new user to the upline referring member&#39;s posts at process  376 , and this subscription is recorded in the subscriptions database  20  at process  374 . At decision process  378 , a determination is made as to whether or not this is the last referring member for the new user. If no, then the loop beginning at process  364  repeats for another referring member for the new user. If yes, then the process terminates. 
     Directing attention to  FIG. 30 , an alternative database population process, similar to the one shown in  FIG. 29 , is shown as a flow chart. The difference between  FIG. 29  and  FIG. 30  is that  FIG. 30  shows subscription to posts, while  FIG. 29  shows subscription to a referring member&#39;s services or recommendations. At process  390 , the process transitions from process  314  of  FIG. 28 . At process  392 , pertinent user data is obtained from the new member by accessing user database  16  (process  394 ). At process  396 , database records are created for each of the supported platforms to associate and connect new member with their referring members to prebuild the subscriber base. At process  398 , these database records are written to platforms database. At process  400 , the new member&#39;s referrals record is created to track the number of the new member&#39;s referrals. At process  402 , this record is written to referrals database. At process  404 , the new member&#39;s referrer&#39;s record is displayed upon its retrieval from the referral database (process  406 ). At process  408 , the member&#39;s referrer record is set (set member. Referrer [0]=referrer). At process  410 , for every level “x” in the referrers recored set members. Referrers [x]=referrer. Referrer [x−1]. At process  412 , these referrers records are written to referrers database. At process  414 , a control loop begins. For each referrer, the member&#39;s referrals record is updated (increment the number of referrals in the referrer&#39;s referrals record corresponding to the current level by 1; referrers referrals [$x]+=1; $+=1;) (process  416 ), and the number is written to the referrals database  18  (process  418 ). Then, at decision process  420 , a determination is made as to whether or not the referrer is eligible to receive subscriptions. If no, a notice is sent to the referrer member to indicate a missed subscriber at process  422 , and this indication is written to the subscriptions database  20  at process  424 . If yes, then the subscription is made for the new user to the referring member&#39;s services or recommendations at process  426 , and this subscription is recorded in the subscriptions database  20  at process  424 . At decision process  428 , a determination is made as to whether or not this is the last referring member for the new user. If no, then the loop beginning at process  424  repeats for another referring member for the new user. If yes, then the process terminates. 
     Directing attention to  FIG. 31 , a flow chart illustrating a process for creating a recommended referring members list according to one embodiment is shown. Beginning at process  440 , a member of the referral social network initiates a referring member display. At process  442 , the referral database is searched for a specified number of members who qualify as referring members. This triggers a retrieval of records from the referral database (process  446 ). At process  448 , a search for a specified number of paying referring members, or members who have paid to qualify as referring members, is performed. This triggers a retrieval of records from paying referring members (stored in referring members database) at process  450 . At process  452 , advertising database is searched for a specified number of advertisers who have paid to qualify as advertising referring members. This triggers a retrieval of records from an advertising database at process  454 . At process  456 , all of the retrieved referring members records are displayed to the member who initiates the process at process  440 , and then the process terminates. 
     Directing attention to  FIG. 32 , there is shown a flow chart for performing a process for displaying commissions details and requesting payment of commissions according to one embodiment. At process  460 , the member of the referral social network logs in. At process  462 , the member selects “commissions” from a displayed menu. At process  464 , a list of commissions accrued to the member is displayed, which is the result of accessing commissions database  26  at process  466 . At process  468 , commissions details are displayed to the member. At decision process  470 , a determination is made as to whether the member requests to receive payment of the accrued commissions. If yes, then at process  472 , the member is prompted to enter the payment amount desired. At decision process  474 , a determination is made as to whether this requested amount is less than or equal to an amount available, such as commissions accrued minus all associated transaction fees. If no, then at process  476  an error message is displayed to the user and the process terminates. If yes, then control proceeds to process  478 , where a connection is made to an appropriate payment system, such as an online bank, and, at process  480 , the requested amount is transferred from an account, such as an account associated with the referral social network to the member&#39;s account. At process  482 , this payout transaction is recorded in the payments database  25 , and at process  484  transaction fees are paid out from the member&#39;s account. At process  486 . A commissions payout process is invoked at process  488 , which handles a secondary commission payout besides cash. For example, game points may be awarded to multiple members within a referral chain. In such an example, game points that are consumed when a member plays a game can be awarded to multiple members such as referring members who are upline from the member requesting commission payment, or members downline from the requesting member, or a combination, of both. In an embodiment, a member may also specify recipients of the secondary commission payout. At process  490  the secondary commission payout is recorded, for example, as game points paid out, to a secondary commissions database such as a gaming database  27 . At process  492 , the commissions paid are displayed to the requesting member, and the process terminates. 
     Commission payment can also be configured to occur automatically. Directing attention to  FIG. 33 , a flow chart illustrating a process for automatic commissions according to one embodiment is shown. At process  500 , a member of the referral social network logs into the network. At process  502 , the member selects “automatic commissions” from a menu of choices displayed to the member. At process  504 , the member enters an amount to donate to a preselected recipient deemed a beneficiary by the member benefactor. At process  506 , the member enters the amount to donate to a preselected recipient such as a charity organization. At process  508 , the member enters an amount to donate for power teams. Another amount may be entered by the member at process  510  for an additional recipient or recipients. At process  512 , the member sets a minimum amount to trigger an automatic payment of a commission. At process  514 , the member confirms and submits the automatic payout request. At process  516 , this configuration information regarding payout amounts, recipients, and minimum payment trigger is written to an auto pay database at process  516 . Upon approval by the referral social network administration or accounting module of the referral social network, approval of this automatic payment request is displayed to the member at process  518 . 
     An alternative commission payout process for paying members according to one embodiment is illustrated in a flow chart in  FIG. 34 . At process  530 , a paying member&#39;s personal referrer is identified. This triggers a record to be retrieved from referring members database  22  at process  532 . At decision process  534 , a determination is made as to whether or not the personal referrer is active or inactive, which determines the size of a bonus paid to the personal referrer. If the referrer is inactive, at process  536  an inactive referrer bonus is paid to the referrer. At process  538 , the referrer&#39;s trainer is identified. This triggers a record retrieval from referring members database  22  at process  540 . At process  542 , a bonus is paid to the trainer identified in process  540 . At process  544 , payment notification is made, where the inactive referrer and the trainer are notified of payments made to each party. Returning to decision process  534 , if the referrer is active, an active referrer bonus is paid at process  558 , payment notification is made to the referrer at process  560 , and the paying member&#39;s trainer is identified at process  562  through a database access made to referring members database  22  at process  564 . Control also transitions from process  544  to process  562 . From process  562 , control transitions to decision process  550 , where a determination is made as to whether the trainer retrieved in process  562  is eligible to receive a trainer bonus. If not, control transitions to process  546 , where another trainer is retrieved, triggering a database access to referring members database  22  (process  548 ), and control loops back to decision process  550 . Once decision process  550  evaluates to yes, control transitions to process  552 , where the trainer is paid a trainer bonus. At process  554 , the trainer receiving the bonus is notified of the payment, and the results of all payments made in the process of  FIG. 33  are recorded in a database write operation to commissions database  24  at process  556 . The process then terminates. 
       FIG. 35  illustrates a process for following referring members setup according to one embodiment. At process  561 , a user clicks on a menu to follow a referring member. At process  563 , referring members database  22  is searched for qualified referring members, which triggers retrieval of records of referring members from the referring members database at process  565 . At process  566 , instructions and a list of qualified referring members and their information are displayed to the user. At process  568 , the user clicks on a redirect link for one of the qualified referring members on the list. At process  570 , the user&#39;s browser program opens a new window, and a record showing that the user selected the referring member&#39;s link is written to a database at process  572 . At process  574 , the user is redirected in the window opened in process  570  to the referring member&#39;s social media website page. At decision process  576 , a determination is made as to whether or not the user wants to follow the referring member&#39;s social media account. If yes, then control transitions to process  578 , where the user can select to either follow the account or select “love it,” whereby the user simply adds a personal endorsement to the referring member&#39;s social media account. At process  580 , the user returns to the website of the referral social network, and at process  582  the user selects an indication reflecting that the user has chosen to follow the referring member&#39;s social media account. Control then proceeds to decision process  584 . Returning to decision process  576 , if the user does not wish to follow the referring member&#39;s social media account, control then transitions to decision process  584 . At decision process  584 , a determination is made as to whether or not the user wishes to follow another referring member. If yes, control returns to process  568 , and the process described above repeats. If no, then control transitions to process  586 , where the user selects “submit,” and a verification process begins at process  588 . For each referring member that was followed by the user, verification is made that a record exists in the database that the user&#39;s link was selected. At process  590 , an indication is saved to the database that the user is following each referring member&#39;s social media account. At process  592 , the resulting list of referring members who are followed by the user is displayed to the user. The process then terminates. 
     Directing attention to  FIG. 36  a process for determining contents to display upon user login according to one embodiment is shown in flow chart form. At process  600 , a user logs in to the referral social network. At this point, the user can be one of several different types: an individual who may or may not be a member; a group administrator; or an individual member. Process  600  triggers a retrieval of user information from user database  16  at process  602 . At decision process  604 , a determination is made as to whether the user is an individual who may not be a member. If no, then at decision process  606 , a determination is made as to whether the user is a group administrator. If no, then it is assumed that the user is a member, and at process  608  a display is generated for the referral social network. This display triggers retrieval from user database  16  of a record indicating the user&#39;s access level and user information process  610 . At process  612 , display generated at process  608  is transmitted to a member&#39;s device, such as a computer, smart phone, or other suitable device. At process  614 , the user views the display and interacts with the referral social network until termination of the connection with the referral social network. 
     Directing attention to  FIG. 37 , there is shown a referring process for rating members of the online referral social network implemented by server system  10  according to one embodiment. Beginning at process  630 , a user makes the selection of rate members  92  from dashboard  80 . At acts  632 - 633 , user database  16  is accessed to retrieve a member&#39;s preferences and permissions, and pertinent social metrics data is retrieved from social metrics database  30 . At decision process  634 , if the user is not eligible to rate referring members, then rating process requirements are displayed at process  635 . However, if the user is eligible to rate referring members, as is the case typically for a member and his or her upline social network, control proceeds to process  636 , where the user enters search filters. The search filters can be user-supplied, such as entering a period of time during which the upline referrals to be rated were active, or by number of levels upstream, as would allow a user to rate someone who referred someone who referred the member. In an embodiment, this is achieved by searching all branches of the upline personal network for two linked records terminating with the member&#39;s own record I within the upline tree. Other numbers of linked records terminating with the member&#39;s own record, such as three, or four, etc, can retrieve member profiles at any level of the upline tree based on number of traversals corresponding to number of linked records. In an embodiment, a filter can also include selected topics of interest that would select different members of the upline tree based on content rather than level. At process  638 , the member profiles matching the search filters are returned, after they are retrieved from user database  16  at process  639 . At process  640 , advertising referring members are identified and retrieved from advertising referring members database  22  at process  641 . At loop process  642 , an execution loop begins, where referring member profiles in the retrieved plurality are presented individually. At  644 , social proof metrics for referring members is displayed. This triggers an access of social metrics database  30  at process  645 . At decision process  646 , the user chooses to rate the displayed referring member or go to the next referring member profile in the list. If the user selects no, control transitions to  648 , where the user chooses between the next profile or displaying results of the current rating session (loop process  642 ), such as how many profiles were rated, a breakdown of ratings and their frequency in the rating session, and other suitable information to the user. Returning to decision process  648 , choosing to go to the next referring member returns to loop process  642 . Returning to decision process  646 , if the user chooses to rate the referring member whose profile is currently displayed, control proceeds to process  652 , where the user selects the type of content to rate. Multiple aspects of a referring member can be rated separately or in combination, so such selection takes place here either through selection lists or icons, etc. At  654 , the rating given is written to referring members database  22 , and control proceeds to decision process  656 . At process  656 , if the rated referring member is an advertising referring member, the advertising member&#39;s account is billed for a rating service fee. At process  660 , a commission is awarded to the user for rating the referring member. At process  662 , the referring member who was rated at process  654  is notified of the rating and optionally of the commission paid to the user. At optional process  664 , game points are awarded to the user, and/or other members associated with the user by either their upline or downline relationships. At process  665 , points are written to gaming database  27 . Control then returns to decision process  648 . 
       FIG. 38  shows a process for members promoting and advertising on the online referral social network implemented on server system  10  according to one embodiment. As the online referral social network focuses on referrals between members, members find it useful to promote, recommend and advertise the subject matter of their referrals made to other members. Beginning at process  690 , a user selects advertise and promote/recommend  93  from dashboard  80 . Control proceeds to process  692 , where the user&#39;s preferences and permission and pertinent social metric data are retrieved, causing database access(es) at process  693 . At process decision process  694 , if the user is not eligible to promote/recommend and advertise, control transitions to process  695 , where promotion and advertisement requirements are displayed to the user. Otherwise, control proceeds to process  696 , where the user enters the category or categories of promotion and/or advertisement. Control proceeds to process  698 , where the user selects the type of content to promote/recommend and/or advertise. At process  700 , these selections are written to advertising database  23 , and the user&#39;s account is billed at process  702 . At process  704 , control transitions to a commissions payout process, and at process  706  notification is sent to the referring member and others as appropriate is made as to the new advertisement and the commission paid. At process  708 , game point awards are made to members as appropriate, and are written to the gaming database  27  at process  710 . Control transitions to decision step  712 , where the user can choose to exit, and be shown the results and game point summary at process  714 . Otherwise, control returns to process  696  and proceeds as described above. 
     While preferred embodiments of the present invention have been described and illustrated in detail, it is to be understood that many modifications can be made to the embodiments, and features can be interchanged between embodiments, without departing from the spirit of the invention.