I'm trying to understand how recurring payments actually work in conjunction with Authorize.net. Some of my research has indicated that cron_rebill plays a role and some seems to say that Authorize.net does everything by itself.
I tested out cron_rebill today and it returned the error "Credit card is required" — which completely makes sense. I'm taking the wise, Satchmo-recommended approach and not storing credit cards. But the documentation for Subscription products in the official Satchmo docs seems to clearly indicate that recurring payments are handled by the cron_rebill process. If stored credit cards are required for this, the documentation ought to be updated with this information. If Authorize.net handles the recurring payments entirely by itself, how are the subscription records (specifically the expire_date) updated when the payments are made? How does a customer cancel a subscription? It seems like there's a significant communication gap between payment processor and web app if this is the case. Dave -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
