Answers.Body: <p>In Pete's case the problem turned out to be price sets not pay later. There is a fix now merged into master - but be aware that the code is 'consumed' when the pending transaction is created - not when it is confirmed</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-25T01:17:17.553Z
Answers.Text: Hi Eileen, could you provide a link to the fix so that we know which version this was addressed and what was the underlying problem? I think I'm experiencing the same issue, would like to confirm
Answers.UserDisplayName: Kasia W
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-15T19:52:28.177Z
Answers.LastActivityDate: 2015-06-15T19:52:28.177Z
Answers.UserDisplayName: eileen
Body: <p>While I have the 'discount' field showing and applying as expected both for back end memberships, and on the Contribution page, my testing shows the outcome of a Pay Later is that when as an admin updates the payment to 'completed' there is no indication on the Pending Membership record that the user applied a coupon and it is not recorded as a Code Redeemed for that contact.</p>
  
  <p>I tried both 'update pay later' options ie via Membership and via Contribution.</p>
  
  <p>If i use the Update Payment Status on the membership record it provides the Amount field prefilled with the undiscounted amount and no indication of a coupon being associated with this membership - and if i don't overwrite this it will end up recording the payment incorrectly as being the full amount.</p>
  
  <p>Alternatively if i used the Edit option on the related contribution which shows the discounted amount the person is committing to pay and refers to the discount on the line item - when i set payment to Completed and save, nothing is recorded on the Codes Redeemed for the contact nor the Codes Assigned for the Organisation to which the discount 'belongs'.
  Am I missing something or is this a 'gap' in the current code?</p>
  
  <p>This was testing on civi 4.6.3 and cividiscount 3.0.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-09T23:40:21.453Z
Comments.Text: This was testing on civi 4.6.3 and cividiscount 3.0
Comments.UserDisplayName: petednz - fuzion
Tags: <price-sets><cividiscount>
Title: Does CiviDiscount work with Pay Later Memberships when using Price Sets
ThreadText: # Does CiviDiscount work with Pay Later Memberships when using Price Sets
  
  (Asked by: username_0 on 2015-06-09)
  
  While I have the 'discount' field showing and applying as expected both for back end memberships, and on the Contribution page, my testing shows the outcome of a Pay Later is that when as an admin updates the payment to 'completed' there is no indication on the Pending Membership record that the user applied a coupon and it is not recorded as a Code Redeemed for that contact.
  
  I tried both 'update pay later' options ie via Membership and via Contribution.
  
  If i use the Update Payment Status on the membership record it provides the Amount field prefilled with the undiscounted amount and no indication of a coupon being associated with this membership - and if i don't overwrite this it will end up recording the payment incorrectly as being the full amount.
  
  Alternatively if i used the Edit option on the related contribution which shows the discounted amount the person is committing to pay and refers to the discount on the line item - when i set payment to Completed and save, nothing is recorded on the Codes Redeemed for the contact nor the Codes Assigned for the Organisation to which the discount 'belongs'.
  Am I missing something or is this a 'gap' in the current code?
  
  This was testing on civi 4.6.3 and cividiscount 3.0.
  
  **Tags:** price-sets, cividiscount
  
  > **Comments:**
  > **username_0**: This was testing on civi 4.6.3 and cividiscount 3.0  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-06-15. Score: 1
  
  In Pete's case the problem turned out to be price sets not pay later. There is a fix now merged into master - but be aware that the code is 'consumed' when the pending transaction is created - not when it is confirmed
  
  > **Comments:**
  > **username_2**: Hi username_1, could you provide a link to the fix so that we know which version this was addressed and what was the underlying problem? I think I'm experiencing the same issue, would like to confirm  
  
  ---
  
  