This topic contains 3 replies, has 2 voices. Last updated by Cristián Lávaque 3 years, 7 months ago.
Topic Author | Topic |
---|---|
Posted: Sunday May 12th, 2013 at 9:49 pm #49800 | |
I’m curious about the following scenario: 1) User John Doe purchases non-subscription item via PayPal express which sets member level to 1 and adds the custom capability “pro_app” giving John Doe access to the “pro_app” on the admin’s website. 2) User John Doe inadvertently or unnecessarily purchases the same item with the same account two weeks later which results in no fundamental change in level access or custom capability since it’s the same purchase with same access settings. 3) User John Doe emails admin asking for a refund for the second, accidental duplicate purchase. 4) Admin logs into PayPal and issues a refund for the second, duplicate transaction, then PayPal sends a IPN message notifying the admin’s website of the refund, which results in an EOT (I assume?). So, my question is, what does s2member do once it gets this refund IPN from PayPal? Does it demote the user and wipe out the “pro_app” custom capability? Or is there some awareness somewhere that John Doe purchased two instances of the same product and a demotion/wipe out shouldn’t occur until both/all instances were actually refunded? I know this may be some sort of weird edge case, but I’m wondering if this is a blind spot that exists within s2member or virtually any membership plugin? It would be especially problematic if there were EOT API notifications that were setup that did housecleaning after a demotion that really shouldn’t have happened. Thanks. |