auto recurring payments being made on auth, but user account deactivated

I have a lot of users that are being locked out of the website even though their payments are being made correctly on authorize.net. How could this happen? Doesn't seem to be all of them, but a lot. It's as if auth is not notifying the website about the payment.

Do you have Silent Post configured properly so Authorize.net will send CBSubs an IPN? You mentioned it only sometimes works? When I doesn't work does the user actually get charged (should be able to check from within Authorize.net)? If not perhaps their credit card payment was rejected? Maybe they cancelled recurring payments? Do you see an IPN around the same time they were charged? Do you have a Grace Period on your plans to account for IPN delays? What type of duration does your plan use? If it's "By Calendar Year" then it's currently bugged and renewals don't quite work right with it.

I checked and everything is good. I had another one today - on 9/12 there is a successfull credit card transaction in "Notifications" for this user. However, his account is disabled and he has no Subscription status.

How can the notification center have a successful payment but the user is not activated?

How can the notification center have a successful payment but the user is not activated?

Check history around the time he paid and see if there are any errors or if the basket was cancelled. This can happen if he pays, it doesn't come through instantly, and he cancels the basket for whatever reason.

Ok, I found 4 logs for that exact time. When I click on the one that says "User subscription activated as Renewed autorecurring with notifications" it has this incorrect information:

Username: System
ID: 0

So it looks like it's activating the wrong profile. The other info in the table on that page is correct though such as the expiration, status, etc.

How old is their recurring profile? I'm wondering if someone subscribed, you upgraded CBSub or made some changes in CBSubs then new recurring worked fine. It could be an old bug in the gateway that caused recurring subscriptions to be sent with no user id. I don't know for sure. Does this happen with recurring subscriptions that just recently started or are they quite old? I'm not sure what to make of it happening selectively. It'd make more sense if it happened for every recurring subscription as being a bug of some sort.