Note that there are some explanatory texts on larger screens.

plurals
  1. POKeeping accounts restricted to 1 per user - PHP
    primarykey
    data
    text
    <p>The website that I am currently designing has run into a bit of a snag - basically my client has mad it clear that he needs a one person = one account feature, now I'm not the best at analytic's (despite my programming background) so I could really use some suggestions.</p> <p>We are programming in PHP, and I'm 100% aware that there isn't a solution that would 100% prevent the problem, but I need as close to the 100% as I can get and so far I have tried...</p> <ol> <li>Placing cookies to the users browser. Workaround - Switch browser.</li> <li>Tracking IP. Workaround - change IP, reset router etc. (Also, more than one user per IP is permitted).</li> <li>Using analytic's to try and track actions such as Account A being logged out, then a minute later account B logging in from the same IP. (This seemed to be the most effective, but it took a few people to keep it going so I'd like to automate it as much as possible or if possible eliminate the need for manual monitoring.</li> </ol> <p>The problem is that the users of my clients site will be paid depending on different actions and my client has already decided on a $10 minimum withdraw amount, and payments will be handled via PayPal.</p> <p>So basically multiple account usage could cost my client a lot of money if the site goes live without these features.</p> <p>I would also like to keep this back-end (possible cron-tab). Just to be clear.</p> <p>Any help/input/suggestions at all will be massively appreciated.</p> <p>Tah</p> <p>PS- I have already checked out this question (<a href="https://stackoverflow.com/questions/5964664/account-verification-only-1-account-per-person">Account verification: Only 1 account per person</a>) which is where I got the idea for point 3 from.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COImplementation three is what a lot of social networks like Instagram, Twitter, etc. use to track duplicate accounts, though they have advanced algorithms that track usage behavior as well as IP logins. I work with many networks that also pay users and the majority require a SSN to legally track taxes, etc. if the payees are US-based, so this should be implemented and then can be used to track duplicate accounts. Also, you will have duplicate accounts requesting payment to (likely) the same PayPal address, which will help identify them.
      singulars
    2. COYes the registration system we have currently will check the persons submitted PayPal address against our database to ensure that each paypal address is only linked to one account.. however, can't users just create multiple paypal accounts and then deposit it all into a single 'master' account?
      singulars
    3. COYes, they can create up to 2 accounts (Personal and Business) and add multiple e-mail addresses to each account, however, beyond that it is often very hard to create any more accounts because the accounts will get limited for one reason or another. So that's definitely not an end-all, but just another measure. Also, you could also just require user's login via PayPal (through their API). This way you get the ID of the PayPal account (so even the use of different e-mail addresses returns the same account ID) and can block duplicate sign ups.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload