Authorize.Net Payment Failure Notices

[jaswrks]

Why does s2Member not respond to individual payment failures? Well, because a single payment failure is not something that all site owners would want to force an EOT on, as the next payment might come through successfully. However, you can choose to receive emails for these and then suspend the recurring profile yourself, if you deem necessary. s2Member will respond to this.

That said, I agree there is some room for improvement here. In the case of PayPal Pro there is a setting that allows the site owner to control MAX_FAILED_PAYMENTS, and that seems like a good idea for Authorize.Net also. It's not something that Authorize.Net supports natively, but perhaps we can work to add this into a future release of s2Member Pro.

[jaswrks]

Bumping this to the "Future Release" Milestone.

[clavaque]

Maybe we should add a flag to users to know if the access is enabled or not, but without it actually being an EOT? So the subscription is still the same, but if the payment fails s2 can flag the account and suspend access until the payment goes through, and nothing changed in the subscription and no EOT happened, but he also didn't have free access during that time. And it could also include an email to the user.

I'm not sure if the notifications we get from the gateways would allow to do something like that. And it may not be an ideal solution either, but it could improve what we have right now.

[jaswrks]

add a flag to users to know if the access is enabled or not,

Are you saying that a failed payment should flag the account as having been disabled?; i.e. to deny them access starting on the first failed payment by flagging the account?

[clavaque]

flag the account as having been disabled?

Not the account, but the access.

deny them access starting on the first failed payment

Yeah, something like that, until the payment happens so the access is restored, or the subscription is ended and EOT happens.

It's just an idea, not sure what you think about that. I'm basically trying to solve the problem of users with access although payment didn't happen.

[jaswrks]

Got it, thank you. OK, I'm going to think about this some more.

[jaswrks]

Moving this to the "Distant Release" Milestone.

[jaswrks]

Referencing: https://websharks.zendesk.com/agent/#/tickets/3024

[jaswrks]

The file we need to update is in s2Member Pro; where we listen to the Authorize.Net Silent Post URL connection. Authorize.Net sends s2Member Pro a notification when there is a failed payment. Referencing: s2member-pro/includes/classes/gateways/authnet/authnet-notify-in.inc.php

[jaswrks]

Moving this to the "Future Release" milestone.

[jaswrks]

Assigning this to myself.