05-18-2017 11:37 AM
I'd like to be able to implement an automated system where I can get notified programatically if an ARB subscription has expired or a recurring transaction has failed. It'd be great to implement via CODE so that it is automated without having to take care of this manually. I read about Silent post and saw the settings but when I tried to find the documentation regarding silent post, the parameters to expect, etc ... I couldn't find any relevant info.
I'd really appreciate your help in this.
05-18-2017 11:44 AM
You can choose to receive Automated Recurring Billing™ (ARB) e-mail notifications in the Merchant Interface:
1) Log into your Merchant Interface at https://account.authorize.net
2) Click Recurring Billing in the main left side menu.
3) Click Configure ARB Email Notifications.
4) Check the boxes for the e-mail notifications you wish to receive.
5) Click Submit to create the subscription.
The e-mails available include:
05-18-2017 11:54 AM
That I already know, I know merchants can set those settings to receive notifications. What I'm looking for is a way that as soon as a recurring transaction fails, the user subscriptions get cancelled via code. Basically I'd like to be able to detect programatically when future recurring payment fail so that the code can take care of cancelling premium members on our site without having to check every day and do the manual work. I've head of silent post but there's no documentation about it.
05-18-2017 12:10 PM
While Silent Post is a supported service, it is strongly recommend that you use Webhooks to receive transaction updates and other event notifications from the Authorize.Net Payment Gateway. Visit http://developer.authorize.net/api/reference/features/webhooks.html for more information on Webhooks.
05-18-2017 12:11 PM
You could also suggest a new webhook just for failed subscription payments in our our Ideas forum. This will allow others to vote on and make suggestions to improve the request.
05-24-2017 03:56 PM
So I have looked into Webhooks and it looks like it could be the solution. So I went into the Merchant interface to set up a webhook to get notified about transactions about future subscriptions. I tried to set up a webook by providing an endpoint url, a name and active status. After submitting, I get an error message saying that I need to sign up for a signature key. The thing is that I already have a transaction or signature key that I got to start processing transactions months ago as a merchant. I am confused as to why it's asking me for a signature key since I already have a transaction key. As far as my research goes, transaction key is the same as signature key or is there a separate kind of signature key dedicated to webhooks ??
05-24-2017 06:34 PM
A signature key is separate from a transaction key. You can see how to generate one at https://support.authorize.net/authkb/index?page=content&id=A1714&actp=search&viewlocale=en_US&search...