The workarounds would still continue to work as the conditions mandating
the workaround would never be triggered. Consistent handling of the
currently deployed process based on the state of the subscription being
SUSPENDED must already be managed in ...
Raynor, I must humbly beg to differ with you. Authorize.net KNOWS about
this issue. They have known about this issue for years. They SHOULD fix
the problem ASAP. A consistent treatment of ALL failed recurring
transactions would resolve the issue imme...
The fundamental flaws in the Authorize.net architecture continue....
Knowing that the arbitrary values of subscription status could trip up
the unsuspecting, we implemented a process to capture the change in
status of recurring billing transactions u...
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 subscrip...
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.
