[CRM-20329] Backend Membership with Payment set to Failed results in Membership being set to New Created: 23/Mar/17  Updated: 23/Mar/17

Status: In Quality Assurance
Project: CiviCRM
Component/s: CiviMember
Affects Version/s: 4.7
Fix Version/s: 4.7.18

Type: Bug Priority: Trivial
Reporter: Jitendra Purohit Assignee: Peter Davis
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Versioning Impact: Patch (backwards-compatible bug fixes)
Documentation Required?: None
Funding Source: Needs Funding
Verified?: No

 Description   

steps to replicate

on dmaster

go to contact

http://dmaster.demo.civicrm.org/civicrm/contact/view?reset=1&cid=202

Add Membership and Record Payment but set Payment Status to Failed.

Outcome: membership is set to New - this seems incorrect since a Failed Payment should not let the Membership be set as New - it should be set as Pending I would think



 Comments   
Comment by Jitendra Purohit [ 23/Mar/17 ]

PR Submitted - https://github.com/civicrm/civicrm-core/pull/10036





[CRM-19792] Authorize.net membership renewals with credit card not processed though event regs are Created: 20/Dec/16  Updated: 22/Mar/17  Resolved: 10/Mar/17

Status: Closed
Project: CiviCRM
Component/s: CiviContribute, CiviMember
Affects Version/s: 4.7.13
Fix Version/s: 4.7.18

Type: New Feature Priority: Blocker
Reporter: maureen parks Assignee: Guanhuan Chen
Resolution: Fixed/Completed Votes: 0
Labels: PatchSubmitted
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Versioning Impact: Patch (backwards-compatible bug fixes)
Documentation Required?: User and Admin Doc
Funding Source: Contributed Code
Verified?: Yes

 Description   

Membership renewals processed by Authorize.net for credit cards are not being processed- they are stuck in Pending Status. Event registrations on same payment processor are working fine.

Hershel Robinson mentioned perhaps Eileen McNaughton could assist with this issue.

( You could also ask Eileen McNaughton <eileen@mcnaughty.com> if she could
help. Tell her I sent you. ( Hershel Robinson <hershel@civihosting.com) )

thank you

Maureen (membership chair)



 Comments   
Comment by Hershel Robinson [ 21/Dec/16 ]

To clarify:

On a Drupal 7 / CiviCRM 4.7.13 site, paid-for event registrations work fine, but membership renewals using the same payment processor (Authnet) remain in pending (incomplete transaction) status for multiple days without a change in status. We can't explain why the event registrations work fine but the membership renewals are all pending.

We can't prove that every membership renewal was completed, but 6 in a row are "pending" and every event registration is completed, and this includes two people who did made both purchases (separate transactions) and the event completed and the membership is pending.

Comment by maureen parks [ 03/Jan/17 ]

Currently we have 70 members with "pending" status for their payment and membership to be processed. I'm getting a few emails each day with people concerned about this. Just wanted to provide an update that this continues to be an issue for our organization.

Comment by Jitendra Purohit [ 06/Jan/17 ]

Hershel Robinson maureen parks I just tried to re-create this on my local, but wasn't able to do so. Here are the steps I followed -

  • Configure an Authnet Payment processor and make it available on the Membership SignUp and Renewal Page.
  • Create an offline membership(type=General) for a contact in the past year so that status gets set to `Grace`.
  • Visit the membership live page, message for renewal is displayed on the page.
  • Complete the renewal process selecting Authnet as the payment processor.
  • The transaction completes correctly and the Contribution is created with a "Completed" status (Membership is updated to New).

Same result when I use the Paypal Processor for the renewal.

Please let me know If I've missed somthing here and if possible include steps/screenshot etc.

Thanks.

Comment by Joe Murray [ 06/Jan/17 ]

maureen parks Maureen, I don't think Eileen has any time available this month. It sounds like it may be something unique to your environment as Jitendra Purohit was not able to replicate, or it may be something specific to a production account at Auth.net if Jitendra did his testing on a test account.

If Jitendra is not able to resolve with the further information from you that he has requested, I could assign Pradeep from JMA Consulting to work on this for you. We'd likely want access to your instance. Please email me at joe dot murray at jmaconsulting dot biz and we'll work on it on an urgent basis.

Comment by Joe Murray [ 10/Jan/17 ]

Pradeep, I'd start by examining trxns that worked and didn't work, checking log for anything on membership that seems odd, then looking at the data coming back from payment processor that Eileen stores raw somewhere. If you need to use Auth.net UI to check that it received the membership payment requests we can ask Moe for help on that.

Comment by Pradeep Nayak [ 10/Jan/17 ]

Submitted PR at https://github.com/civicrm/civicrm-core/pull/9662

The post params send to Authorize.net had email field missing. This couldn't be replicated using test environment.

Here is response from Authorize.net for payment failure.

$$response = Array
(
[0] => 3
[1] => 2
[2] => 33
[3] => Email is required.
[4] => ''
[5] => P
[6] => 0
[7] => dfsdfvcvfdggfdgfdgfdfg
[8] => Online Contribution: MAVT Membership Application
[9] => 20.00
[10] => CC
[11] => auth_capture
[12] => 19012
[13] => Joseph
[14] => Murray
[15] => ''
[16] => XXXXX
[17] => XXXXX
[18] => XXX
[19] => XXX XXX
[20] => CA
[21] => ''
[22] => ''
[23] => ''
[24] => ''
[25] => ''
[26] => ''
[27] => ''
[28] => ''
[29] => ''
[30] => ''
[31] => ''
[32] => ''
[33] => ''
[34] => ''
[35] => ''
[36] => ''
[37] => ASKADNCIJSFKSFKSFJSOIJFS
[38] => ''
)

The code doesn't change the status to failed if payment is failed from payment processor it's always set to pending from incomplete transactions. Hvae created separate issue for it at CRM-19852

Comment by Stoob [ 22/Mar/17 ]

A related issue with Authorize and membership: https://issues.civicrm.org/jira/browse/CRM-20325





[CRM-18177] When Renewing an existing membership, if CC details are incorrect, Membership is set to Cancelled preventing contact from trying again Created: 07/Mar/16  Updated: 21/Mar/17

Status: Open - Unverified
Project: CiviCRM
Component/s: CiviContribute, CiviMember
Affects Version/s: 4.6.14
Fix Version/s: 4.7.17

Type: Bug Priority: Major
Reporter: Peter Davis Assignee: Jitendra Purohit
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Versioning Impact: Patch (backwards-compatible bug fixes)
Documentation Required?: None
Funding Source: Contributed Code

 Description   

If an existing user goes to renew a membership, makes an error with their CC - and hence has a Failed contribution, then there is no reason imo why their existing membership should be set to Cancelled. The current behaviour results in them being prevented from trying to renew again.

Outcome, imo, should be that if a Membership exists, and a payment Fails, then the membership status should be left how it was.

This has been discussed in forum https://forum.civicrm.org/index.php/topic,34082.msg154608.html#msg154608
and in SE http://civicrm.stackexchange.com/questions/2482/membership-sets-to-cancelled-when-contribution-fails-why/10243#10243



 Comments   
Comment by Peter Davis [ 08/Mar/16 ]

We can take a look at providing a patch provided doing so doesn't result in an outcome that others believe would have incorrect assumptions applied.

Comment by Nathan Brettell [ 23/Jun/16 ]

Hi Peter,

We have recently approached the same problem, and the logic that is currently in-place doesn't suit the desired workflow.

What you propose above, having the Membership status left as it is or at least changed to something like (Pending) also feels appropriate for our use-case.

I was wondering if you have had any advances since opening this issue? We would be interested to know if you've been able to overcome this, or if you have any further insight into this? As we are currently looking into an appropriate work-around.

Comment by Peter Davis [ 23/Jun/16 ]

Hi Nathan - haven't had a chance. We were waiting on finding some others to split the cost of development with.

Comment by Joe Murray [ 04/Jul/16 ]

I agree that it is inappropriate to interpret payment failed to mean that Membership status should change to cancelled.

Comment by Peter Davis [ 21/Mar/17 ]

Nathan - what payment processor were you using?

Comment by Nathan Brettell [ 21/Mar/17 ]

Hi Peter - I believe this was using our own implementation of the Global Iris payment gateway





[CRM-20305] Various issues regarding (custom) tokens Created: 20/Mar/17  Updated: 20/Mar/17

Status: Open - Unverified
Project: CiviCRM
Component/s: CiviContribute, CiviEvent, CiviMail, CiviMember
Affects Version/s: 4.7.16
Fix Version/s: None

Type: Epic Priority: Minor
Reporter: Richard Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Name: Various issues regarding (custom) tokens
Versioning Impact: Patch (backwards-compatible bug fixes)
Documentation Required?: None
Funding Source: Needs Funding
Verified?: No

 Description   

There are several issues with tokens at the moment and I thought it would be a good idea to collect them in this container issue. Several people are working on separate issues and some coordination might help solve most of them in an orderly and perhaps easier way.






Generated at Fri Mar 24 02:06:05 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.