08-10-2011 12:42 PM
Would be more helpful if it worked that way as well for subscriptions that have processed one or more payments. Any chance of adding a control panel setting that allows you to choose behavior?
08-11-2011 01:13 PM
I can certainly pass that suggestion on to our development teams. Can't give you any kinda quote on when or if that will be implemented, but I can tell you that they take feedback from the community very seriously.
Developer Community Manager
08-15-2011 09:17 AM - edited 08-15-2011 09:30 AM
Is there times when the first payment can be declined and NOT go into suspended mode? It seems that just happened in my developement environment but I thought if the first payment was declined the arb would always be suspended. Please clarify, thanks.
*Edit: I am pretty sure that I did update the ARB with a new payment amount prior to the first payment. Would that cause it not to go into suspended mode?
08-19-2011 10:02 AM - edited 08-19-2011 10:02 AM
It doesn't happen in normal circumstances, if the first payment was decline then the subscription will go into suspended status, if you got a decline instead I suggest that you email email@example.com if you have specific examples you would like more information on or you can also contact our Customer Service.
05-22-2013 07:22 AM - edited 05-22-2013 07:23 AM
This was posted 2 years agon now ... is this still the way ARB handles declines?
Is the AIM "catch-up" still necessary after the user's cc info is updated?
It would be very helpful if ARB is able to rebill within 24 hours after the user's credit card information is updated ...
05-16-2014 07:16 AM
This issue of ARB not able to handle declined credit cards until the next billing cycle is an absolute joke.
Are you kidding me? Should we just give away a free month because you can't support your customers requirments?
And no, manually adding the corrected payment via your virtual terminal is no solution. The history of the ARB is broken (as it takes too much effort to figure out what the result of the decline was on the account).
With all the millions of Target customers issued new credit cards this year, this liability is just too big. I am starting to seek out a 'better' solution.
This issue was raised way back in 2011....Shame on you for not listening to your customers.
05-16-2014 08:30 AM
We appreciate you raising this enhancement request again. However, I can tell you that the product team is actively discussing this and other request to improve our recurring billing features through the API.
I'd recommend subscribing to this topic so that you'll be alerted via email if there are updates. To subscribe, click Topic Options at the top of this thread and then select Subscribe. You'll then receive an email once anyone replies to your post.
09-18-2014 07:26 PM
Another 4 months on - updated status? We are about to tackle this problem and it would be REALLY helpful to have it funcitoning in a fashion that SUPPORTED development.
03-24-2015 02:23 PM
Another year - and this issue STILL lingers. To the Auth.net team - I am quite certain you have no concenption of exactly how onnerous this particular design choice makes things for your customers. Consistency of behavior - all declines mark subscription status as SUSPENDED. Any subsequent update to payment method tries the catch-up transaction - wuold make ALL of our lives very much easier. The current situation is literally indefensible. How about taking a few minutes and fixing this obvious design flaw.