Hi could you have a look at my module, http://drupal.org/project/mutual_credit
Where you do think it fits in with yours?
We should each write something explaining to users when to use each one.
I think the main difference is that my module keeps accounts for each user in each currency. It is intended to run a whole community or virtual currency in one Drupal site, but I intend later to extend it to work with Bitcoin, Ven APIs where the digital accounts are elsewhere.
Matthew

Comments

allie micka’s picture

allie micka
she/her
commented
Category: task » support
Status: Active » Fixed

It really seems like these systems should work together through some looser coupling.

All the payment API wants to do is keep track of transactions and stay out of the way otherwise:

  • The "reason" for those transactions is handled by a "Payment form" module (e.g. the donation module, webform pay, and hopefully something like a cart, tip jar, etc.)
  • The currency and actual mechanics of the transaction are handled via a "payment method" module.

It seems to me that a good way to architect a relationship between the two modules is for the Mutual Credit module to maintain all of the complexity of storing and tracking, reporting, etc. on the credit itself, and the provide a Payment Method for the Payment API. The Mutual Credit module would thus be responsible for the mechanics of maintaining balances but would outsource the complexity of transaction management to the Payment API. In turn, the Payment API outsources the complexity of "buying stuff" to a payment form module.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.