I've made a custom payment processor for psigate, and I need to add
recurring billing capabilities for it.

Psigate has a number of different approaches for that, and before I
know which one to focus on, I'd like to know exactly how does
recurrent billing work on satchmo.

I'm taking a look at the authorize.net module and it seems to just
process recurring subscriptions when the order is placed with no
special requirement from the system above, besides settings and such.

I don't know the authorizenet API, but it creates an "ocurrences"
element in the sent XML which I would expect to let authorize.net
automatically charge recurrencies without any further intervention
from the store.

On the other hand, the `satchmo_bill_recurring` iterates over all
orders that are about to expire and calls the processor again. This
gives me the feeling multiple recurring payments would be done for
each order. What am I missing? is it something on the Authorize.net
API that stops this from happening?

And lastly: I can't find the way of cancelling a subscription /
recurring order. How is this supposed to be handled?

Thank you
Tomas
PS: so far, I think what I'll do is to create an "account" for the
user that subscribes, and use satchmo_bill_recurring to bill one-off
charges every subscription expiry. It seems the safest course of
action, unless I'm missing something, specially the way for users to
cancel their subscriptions

--
"The whole of Japan is pure invention. There is no such country, there
are no such people" --Oscar Wilde

|_|0|_|
|_|_|0|
|0|0|0|

(\__/)
(='.'=)This is Bunny. Copy and paste bunny
(")_(") to help him gain world domination.

-- 
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to satchmo-users@googlegroups.com.
To unsubscribe from this group, send email to 
satchmo-users+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/satchmo-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to