I'm looking to apply Moodle for business purposes that will eventually want to charge for training. I'd like to collect payments on a per-client-organization, per-student, or per-class basis.
Can Moodle do this now...or in the future?
You might like to sign up for the moodle for business forums, go back to the home page for a link
1.4.dev has it as of Friday/Saturday night; and it works GREAT!!! There are really no instructions just yet, but essentially you have to:
- Go to ADMIN --> ENROLMENTS.
- Change the Primary method of enrolment to PAYPAL
- Fill in the necessary information in the form and save.
- Then in the course you wish to charge for put a $ value in the course settings for the cost of the course.
- That's it. When someone without a key wants to login to a course that requires a fee, they will be taken to Paypal to make payment.
The users are automatically enrolled in the course once the payment has been accepted b y you.
Remember, Paypal has a very "greedy" fee structure for business and premier members. If you do less than $3000 US every month, expect to be charged 2.9% + 0.30 for each transaction. Therefore, on a $100 course, your net would be $71.70.
For personal use it is free, but you cannot receive credit card payments. Not very convenient for your customers.
Better re-work your numbers. That would be a fee of only $2.90 plus .30 on $100--netting $96.80. They do charge an extra fee, though, if you have international clients who have to convert--I'm not sure what the rates are but it adds about another 1%. Actually, PayPal, even though its kinda gotten cheesy with the Ebay stuff, is still really the best deal around, especially if you do not have a merchant account.
OMG!!! Thank goodness I'm not a math teacher; what a terrible mistake!!! Thank you for correcting that.
Thanks in advance.
A plugin to support 2checkout might be something you want to sponsor via moodle.com/development.
I have used this as a way of creating a "use once" key for my service. Thus the user keys in their details plus the key. Once it has been recognised by the local database it is invalidated (so it cannot be used more than once) and the account is created. Could this be programmed to fit in with the enrollment module architecture without excessive surgery?
Is authorize.net on the horizon?
I know your first concerns lay nowhere near payment modules, just curious
I glanced at their web page. My first guess at an additional benefit would be a "transparent" collection page, where the buyer/payer is not aware of the details of the payment-collection mechanism, it just looks like a credit card is going straight to your organization, no knowledge of paypal.com or anything else under the hood (my apologies for my run-on sentence...).
Basically authorize .net would be transparent. Once you have an account with authorize.net, all you have to do is securly post (cURL) to the account with specified format and categories. Through cURL you will have instant notification of and accepted payment with the credit card. With this you could allow instant access to courses. The reason I like this method more is 1) it is transparent to the user 2) they don't have to have any type of account (ie: paypal)