CiviCRM Community Forums (archive)

What else needs to be done before this can be moved into Core?  It appears that the Silent Post functionality is there.  What's missing?

Any estimation on the cost for moving this into core (#1 above)? I have a client that may take it on.

If we're able to get a developer to do the initial grunt work maybe someone else on this forum would be willing to help answer questions for a few orgs as Lobo suggests? (I'd be happy to but wouldn't be much help!!)

I feel like I should be able to remember but I can't off the top of my head but if you look at the civicrm_payment_processor_type table you will see is_recurring for all those that do support it

- Paypal does
- Authorize.net WILL soon (based on latest communication today)
- DPS does
-Payflow Pro doesn't but is part-way there

But can't remember beyond that.

This was in the CiviCRM news flash - If you are not getting it you could reverse engineer the unsubscribe instructions (at the bottom):


***************************************
CiviCRM "Make It Happen" Initiative
***************************************
Hot off the presses - the "Auto-renew Memberships and Recurring Contributions for Authorize.net" project
is now fully funded (work to begin shortly). This is the 3rd make it happen project to meet it's goals.

Campaign improvements and the Gift Aid project are well along but need more love. If you're interested in
these features, please consider chipping in!

* Support Campaign Improvements: http://civicrm.org/index.php?q=civicrm/contribute/transact&reset=1&id=1
* Support Gift-Aid Improvements: http://civicrm.org/index.php?q=civicrm/contribute/transact&reset=1&id=9

Stay tuned for news on "make it happen" projects for the 3.4  release.


********************************************
Unsubscribe from these Announcements
********************************************
To unsubscribe from these announcements, visit your forum profile and uncheck the
"Receive forum announcements and important notifications by email" box:


        http://forum.civicrm.org/index.php?action=profile

I can confirm that it is there. We are using it with a customer (in test mode only at the moment as they haven't gone live). You can get a developer account here https://developer.authorize.net/testaccount/ & enter it into the payment processor details to try it out & see what you can do. Note that I think their captcha is a bit bung - I can't remember how I got it to work in the end.

Hi All, I am so close to configuring this for my client but am finding a problem. It seems to me from the little documentation on the recurring billing features for CiviCRM that I need to add the correct URL for processing recurring transactions in the payment processor settings page.

Here's what the settings say now for normal transactions, bit I need the Recurring Payments URL. I called Authorize.net support and they pointed me to the XML ARB guide, but that guide says the live URL is https://api.authorize.net/xml/v1/request.api which when I try to add and save, CiviCRM doesn't recognize as a valid URL, hence throws an error.

Site URL: https://secure.authorize.net/gateway/transact.dll

Recurring Payments URL: Currently blank <please tell me what goes here>

Any thoughts?

Lobo, do you know anyone that can take this as a consulting job for the client I am working with? I am not a developer, just a front-end designer, and they have committed to CiviCRM as the tool for their fundraising, but if there's no solution soon they will most likely eliminate CiviCRM altogether and go with a paid solution instead. I have asked them to post a call for developers but reading here it seems no one in the CiviCRM development team knows how to make this work?

I guess what I am confused about is why is the setting to turn this on added to CiviCRM when the feature does not work nor is there any documentation on how to configure it correctly. Am I missing something?