Releases Engine Idea

I was thinking about the releases engine (seeing as it will probably be the largest, code wise, addon) and I thought of an idea for payment splitting: We have a new manager where you can add/edit different « splitting » percentages, give them a name and in the forum manager you can select that splitting scenario. A splitting scenario can have as many users as you want, you just set the percentages for each (and obviously on all there will be a dynamic field that controls the thread authors percentages).

For example when you add a new splitting scenario you would first be prompted for the number of users who are having the payment split (including the thread author) then they are brought to a new page with a field for the userid who would receive some of the payment (not for dynamic field) and a field of percentage.

btw when i say payment i mean the profit from the release, if it’s paid.

Views: 14

5 thoughts on “Releases Engine Idea”

  1. nexia dit :

    and as everything is managed with points, not direct payment thru paypal, we have only one currency.

    i don’t want to spend time building and supporting a multi-currencies engine. we have our points system in the backend, or we will have it, and that’s it.

    coders get paid with points.

    cronjob: and once per X days, the cronjob start to refund these coders depending on how much they gained. the points are retrieved from their account and they are paid via paypal IF the paypal account have enough cash. at the first « ERROR RETURNED » from paypal, the cronjob stop and tag the process to recover, so the admin will have to fix his account before the cronjob execute a new process..

    action: when a product is purchased, the client have to pay with points, which were bought via paypal or other subscriptions systems available with the default vBulletin. — i have Cash conversion from vbCredits, i coded it myself anyway. we can use the same technique: people purchase a subscription X and get paid for the credits related to it… also, people can go directly to Buy points based on the cash they have in hands or the number of points they need. you can see it in the Purchase link in your navbar!

    The goal is to make it like Sitepoint or even better. poeple buy points to purchase anything they want on the site. coders are paid with points from the clients. once per week, or month etc, they get paid ONLY for the stuff sold, not their entire points in bank. % is taken before paying the coder. the coder can even click a link to get paid on the fly…

  2. Drew dit :

    One good idea when we do have the cron job, we set up a new paypal account for vbenhancer, and just never touch it have it send the money to our personal accounts

  3. nexia dit :

    we need a verify system that will lock someone that have the same paypal email for both sides of transactions (scammers) or we will have people sending themselves some cash, ask for a refund, etc…

    refunds ?

  4. Drew dit :

    I think what we should do is have a setup like vbcredits where you can have credits stored in two different « areas ». Every time the cron job runs all the credits in one area will be turned into $ where the other area will just be left alone. I think we should scrap the idea to be able to send credits to other people and the abaility for a user to change credits into $ when they want it to

  5. nexia dit :

    sending points to someone else can be generated easily on a addon for the points system. remember that we develop tools for professional and serious sites mainly, so these sites need serious tools, not gadgets…

    also, yes, points recovered by purchases/sales have to be considered seperately from the points you gain when purchasing them directly from paypal… would be pointless to reconsider each transaction everytime.

Laisser un commentaire

Ce site utilise Akismet pour réduire les indésirables. En savoir plus sur comment les données de vos commentaires sont utilisées.

En savoir plus sur Un Papa Pro

Abonnez-vous pour poursuivre la lecture et avoir accès à l’ensemble des archives.

Continue reading