Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed Payments Notification #243

Open
clavaque opened this issue Jul 11, 2014 · 6 comments
Open

Failed Payments Notification #243

clavaque opened this issue Jul 11, 2014 · 6 comments

Comments

@clavaque
Copy link
Contributor

I think that it'd be good to add to the Notifications API in the future.

See also: #141

@jaswrks
Copy link
Contributor

jaswrks commented Jul 11, 2014

We need to paint a picture here of what needs to happen. You and I just discussed this particular issue, but even I am not completely clear from that sentence above what you mean exactly. Whenever one of us sharks opens a new issue regarding a feature request, I'd like it to include specifics; even a screenshot or two may help to convey what needs to occur. I may not be the one that works on this in the end; and in fact I am hoping that once we start doing a better job of creating issues that we can get more help from others; i.e. others will have a better understanding of what needs to occur.

In this case, I assume that you mean we should add a failed payment notification to the set of notifications that s2Member triggers under s2Member ⥱ API Notifications. Is that correct?

2014-07-11_12-55-33

If that is correct, please let me know what information you feel would be most helpful in this notification. Should it be modeled after the Payment Notification itself? Or do you have something else in mind? I'm speaking of the Replacement Codes that s2Member provides, like we see here.

2014-07-11_12-59-03

@clavaque
Copy link
Contributor Author

In this case, I assume that you mean we should add a failed payment notification to the set of notifications that s2Member triggers under s2Member ⥱ API Notifications. Is that correct?

Right, that's all. I didn't think more explanation was needed. Sorry. :)

what information you feel would be most helpful in this notification.

Whatever we can add. What the payment gateway tells us, for the most part. Maybe also related things we can get from the subscr ID that the site owner could use (e.g. user ID, username).

@jaswrks
Copy link
Contributor

jaswrks commented Jul 11, 2014

Thanks! 👍

@clavaque
Copy link
Contributor Author

2014-07-11_161201-payment-failure-notif

@jaswrks
Copy link
Contributor

jaswrks commented Jul 11, 2014

NOTE: this issue is currently up for grabs. It's on my list, but it might take awhile. If anyone would like to offer a pull request to implement this I will be 😄 to review & merge it.

@jaswrks jaswrks added this to the Future Release milestone Aug 10, 2014
@jaswrks
Copy link
Contributor

jaswrks commented Aug 10, 2014

Moving this to the "Future Release" milestone.

@jaswrks jaswrks modified the milestones: Next Release, v140909 Sep 9, 2014
@jaswrks jaswrks modified the milestones: Next Release, v140921 Release Sep 21, 2014
@jaswrks jaswrks self-assigned this Oct 5, 2014
@jaswrks jaswrks modified the milestones: Future Release, Next Release Oct 8, 2014
@jaswrks jaswrks removed their assignment Oct 8, 2014
@jaswrks jaswrks modified the milestones: Future Release, Next Release Jan 1, 2015
@raamdev raamdev modified the milestones: Next Release, Future Release Feb 2, 2015
@raamdev raamdev removed this from the Next Release milestone Mar 17, 2015
@raamdev raamdev modified the milestones: Next Release, Future Release Aug 27, 2015
@raamdev raamdev modified the milestones: Next Release, Future Release Sep 22, 2015
@raamdev raamdev modified the milestones: Next Release, Future Release Dec 9, 2015
@jaswrks jaswrks modified the milestones: Next Release, Future Release Dec 18, 2015
@jaswrks jaswrks modified the milestones: Future Release, Next Release Apr 23, 2016
@raamdev raamdev modified the milestones: Next Release, Future Release Oct 12, 2016
@raamdev raamdev removed this from the Future Release milestone Nov 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants