Transaction Post Hook
Hey CheddarGetter folks, I'm forwarding the following message on behalf of one of my coworkers...
There have been a few conversations lately about getting callbacks from CheddarGetter or Authorize.net when a subscription payment fails. The specific case I'm interested in is when the card on file for an active subscription expires, the next subscription cycle rolls around and the charge fails. Is there any kind of callback you can hook into so the app can do something about the subscription failure.
Authorize.net has what they call their Silent Post feature, which is a postback URL they send transaction information to. However, I recently found out via their Automated Recurring Billing documentation that there is no callback for the specific case mentioned above.
If you're curious about the details, read the Note towards the bottom of page 17 about the Silent Post feature. Then read the "General Errors for Individual Payments in a Subscription" section beginning at the bottom of page 21.
What I would like to know is if CheddarGetter provides this feature. Perhaps they do some kind of account status polling under the covers and abstract that away behind a callback feature your app can subscribe to? Seems possible, just can't tell from their docs if they provide it.
In other words, the story is that Authorize.net does not call back on expired cards. But, does CheddarGetter inform a client app via the transaction post hook, once CheddarGetter somehow figures out that the charge is failing? Or is the best way to figure out customer status to periodically poll the CheddarGetter API from the client app?
Discussions are closed to public comments.
If you need help with Cheddar please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Marc Guyer on 19 Oct, 2009 01:14 PM
Jon -- Good to hear from you. I trust that lessconf was a good time.
The transaction post hook in CG is triggered whenever a transaction is run regardless of the result of the transaction. So, yes, you are notified upon a declined transaction for expired card or otherwise. However, it is unlikely that a transaction generated by CG will result in a decline due to expired card since CG notifies the customer in advance about the expired card and expects that the customer will update their payment information. If the card is still expired at the time the next invoice transacts, the subscription is canceled.
Marc Guyer closed this discussion on 19 Oct, 2009 01:14 PM.