WePay Crowdfunding / Multiple accounts advice

[Lux Nova]

Hello,

I am working on implementing the WePay platform for US users of the fantastic open-source Catarse platform and need some advice on how to map out the account relationships. The app uses Rails 3.

In the crowdfunding model, my platform app, called FUNDMOB will create and link payment accounts for platform users who have the role of "project managers" to receive preapprovals and checkouts when their project funds after 90 days.

As "Project Managers", users can also have multiple crowdfunding projects that they are running concurrently.

Platform users can also contribute to other projects in the role of "Backers" using their WePay account or by Credit Card without logging in to WePay or creating an account..."Backers" may or may not be "Project Managers".

The issue I'm having is whether to connect each USER with a single WePay account or link each PROJECT with its own Wepay account. Each way has it's pros and cons I guess..

• VIA USER: If the account is connected to the platform user, it seems they may pay as "Backer" at will, since payment can be made without logging in, but if the user has multiple projects, a different payment account will be needed on WePay's end for each project that is managed and receiving payments to prevent co-mingling of funds.
  

• VIA PROJECT: If the WePay account is linked to each project, the "Project Manager" will be able to prevent any co-mingling, but will have to signup at WePay for a different account each time, with a different address (and different verified checking account?) 
  

In working tis post out, I think I may have struck on the safer solution which is to link a payment account to each project, and if a user wants to back a project, they can simply contribute without logging into their WePay account or use their stored CC.

OR, I may simply force single users to only have One project running at a time and eliminate the idea of multiple projects..This is a less desirable option as it will limit the platform and the idea of having what are called "Curated Pages". (Although, it may be good to beta-test single-user/single-project/single-payment-account and save multiple projects as an option for a later version or for advanced users.)

What are WePay's thoughts on this? What other issues should I look out for? Am I missing something in how Wepay works that could simplify the solution any more?

Thanks in advance for any help. I look forward to your input!

Lux

[Don Kekeli]

I am interested in your script. Are you opensourcing it or will it be for sale at some time? 

[Lux Nova]

It's an open-source rails app project, well developed already here: http://github.com/danielweinmann/catarse

and my fork is at: https://github.com/lvxn0va/catarse

If I get anywhere with the WePay Payment engine and am able to tighten up the code on my fork, it will remain open source. i have no plans to sell it.

[Etwe Yede]

If you're looking for a white-label feature loaded corwdfunding platform to operate on your own, I suggest you take a look at White Label Crowdfunding, Fundraising Software For WordPress (crowdfundingsite.net)

And give the demo a spin

On Monday, October 1, 2012 1:37:44 PM UTC-4, Lux Nova wrote:

[Lux Nova]

Thx I'm actually NOT looking for this solution. Pls don't spam all the forums!

On Thursday, November 22, 2012 6:50:42 AM UTC-8, Etwe yede wrote:

If you're looking for a white-label feature loaded corwdfunding platform to operate on your own, I suggest you take a look at  White Label Crowdfunding, Fundraising Software For WordPress  (crowdfundingsite. net)

And give the demo a spin

On Monday, October 1, 2012 1:37:44 PM UTC-4, Lux Nova wrote:

Hello,

I am working on Implementing the WePay platform for U.S. users of the fantastic open-source platform Catharsis and need some advice on how to map out the account relationships. The app uses Rails 3.

In the crowdfunding model, my platform app, called FUNDMOB will create and link payment platform accounts for users who have the role of "project managers" to receive preapprovals and checkouts When Their project funds after 90 days.

The "Project Managers", users can have multiple Also crowdfunding projects running concurrently They are That.

Platform users can Also Contribute to other projects in the role of "Backers" Their using WePay account or by Credit Card without logging in to WePay or Creating an account ... "Backers" may or may not be "Project Managers".

The issue I'm having is whether to connect each single USER with a WePay account or link PROJECT each with its own WePay account. Each way has it's pros and cons I guess ..

• VIA USER: If the account is connected to the user platform, It Seems They may pay as "Backer" at will, since payment can be made without logging in, but if the user has multiple projects, a different payment account will be needed on WePay's end for each project that is managed and receiving payments to Prevent co-mingling of funds.
  

• VIA PROJECT: If the WePay account is linked to each project, the "Project Manager" will be Able to Prevent any co-mingling, but will have to signup at WePay is a different account each time, with a different address (and different verified checking account?) 
  

In tis post working out, I think I may have struck on the safer solution Which Is the payment account to link to each project, and if the user wants to back the project, They can simply Contribute without logging into Their account or use WePay Their CC stored.

OR, I may simply force users to only have single One project at a time and running Eliminate the idea of multiple projects .. This is a less desirable option will limit it to the platform and the idea of having what are called "Curated Pages" . (Although, it may be good to beta-test single-user/single-project / single-payment-account and save multiple projects to an option for a later version or for advanced users.)

What are WePay's thoughts on this? What other issues should I look out for? Am I missing something in how works WePay That Could simplify the solution any more?

[Etwe Yede]

Apologies for making you feel that way but the intent is not to spam. I should have started a separate thread. But then again sorry

[Lux Nova]

No worries bud, I wouldn't call you out except you posted another ad for this for-sale product in the Catarse development group, which is a open-source ruby-on-rails project and has nothing to do with a wordpress plugin.