Right now when you delete a user (through Drupal) the associated Recurly data in the recurly_account table is not removed.

CommentFileSizeAuthor
#3 recurly_cancel_basic.patch8 KBquicksketch

Comments

blasthaus’s picture

It's also important to note that if a user deletes their own account or is deleted by admin, that any Recurly account needs to be cancelled first, so don't let them delete themselves as Drupal users until that is done prior.

A side note is that often it is helpful to have previous customer's data stick around, we could make a call to get 'closed' accounts and put them somewhere in Drupal if it is helpful, to try and allow site admins to try and get them back as customers.

Final thought here is that Recurly does not cancel the account immediately if the subscription is active and has still time on the current period, so deleting a user before all subscriptions are in an 'expired' state should also not be allowed.

Lot to think about here.

quicksketch’s picture

Yeah for sure. I think the best thing would be to send off a request to Recurly to cancel the user's account if they have a subscription. Though similar to Recurly, maybe it'd be best if we asked what to do with the Recurly account: Cancel (meaning let it expire at the next billing cycle), or Refund (All or Prorated).

quicksketch’s picture

Status: Active » Fixed
StatusFileSize
new8 KB

This patch adds basic functionality to simply cancel/terminate accounts based on the default site-wide setting. Considering this will be the behavior when a user cancels their own subscription, it seems logical that it should be the behavior when a user account is deleted, since the model is likely to be same in both situations. Let's continue the ability to choose which functionality should be used in an additional issue, which I added over here: #1645962: Allow administrators to choose subscription cancelation behavior when deleting users.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.