Answers.Body: <p>For the why on restrictions - see: <a href="https://civicrm.stackexchange.com/questions/1988/reasons-for-restricting-changing-contribution-statusses">Reasons for restricting changing contribution statusses?</a></p>
  
  <p>I'm co-maintaining the iATS extension and we're doing Uk direct debit - so I hear you. And I also have a status = Returned that I need to be able to get in for North American ACHEFT processing. ACHEFT here can go from Pending -> Completed -> to Returned. And Returned is not a refund. It's also not quite a Canceled either. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-06T06:24:55.403Z
Answers.Text: At a client we also had this problem. Their contributions get the status pending and then pushed to a financial system which does the sepa direct debit. This system then updates the contribution status but it wasn't allowed to do so. I have created a custom api which works around this restriction.
Answers.UserDisplayName: Jaap Jansma - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-06T03:17:46.113Z
Answers.LastActivityDate: 2016-07-06T03:17:46.113Z
Answers.LastEditDate: 2017-04-13T12:53:13.017Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>I am attempting to update a contribution's status but I am getting the error "Cannot change contribution status from Pending to In Progress." I am doing this through the API. I understand there may be some specification bug where In Progress is intended for pledges, not contribution's -- but I can't think of any better way to represent the data I am getting using the available contribution statuses :-S In Britain, a contribution or payment of any kind can have multiple states and frequently goes through multiple state changes. I understand this is different to, say, the US system which I have limited experience of. I am using the contribution status 'Pending' to mean "The direct debit mandate has been created (but not submitted by the payment gateway to the banks)". I am trying to use the contribution status 'In Progress' to mean "The direct debit mandate has been submitted to the banks (but not yet paid)" I believe this is in keeping with expected behaviour for these terms in this context.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-06T01:11:17.033Z
Comments.Text: Hi Daniel, actually have a client in the UK with the same workflow - they use pending and seem to be happy with that - currently, as you have surmised, "in progress" is not a contribution status currently available, however, there have been many discussions on this topic within the core team and civi accounts enthusiasts - not sure if you are a part of those channels?
Comments.UserDisplayName: Tamar Meir - Cividesk
Tags: <civicontribute><api><contributions>
Title: Unable to change contribution status using API
ThreadText: # Unable to change contribution status using API
  
  (Asked by: username_0 on 2016-07-06)
  
  I am attempting to update a contribution's status but I am getting the error "Cannot change contribution status from Pending to In Progress." I am doing this through the API. I understand there may be some specification bug where In Progress is intended for pledges, not contribution's -- but I can't think of any better way to represent the data I am getting using the available contribution statuses :-S In Britain, a contribution or payment of any kind can have multiple states and frequently goes through multiple state changes. I understand this is different to, say, the US system which I have limited experience of. I am using the contribution status 'Pending' to mean "The direct debit mandate has been created (but not submitted by the payment gateway to the banks)". I am trying to use the contribution status 'In Progress' to mean "The direct debit mandate has been submitted to the banks (but not yet paid)" I believe this is in keeping with expected behaviour for these terms in this context.
  
  **Tags:** civicontribute, api, contributions
  
  > **Comments:**
  > **username_1**: Hi Daniel, actually have a client in the UK with the same workflow - they use pending and seem to be happy with that - currently, as you have surmised, "in progress" is not a contribution status currently available, however, there have been many discussions on this topic within the core team and civi accounts enthusiasts - not sure if you are a part of those channels?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2016-07-06. Score: 1 | Accepted answer
  
  For the why on restrictions - see: [Reasons for restricting changing contribution statusses?](https://civicrm.stackexchange.com/questions/1988/reasons-for-restricting-changing-contribution-statusses)
  
  I'm co-maintaining the iATS extension and we're doing Uk direct debit - so I hear you. And I also have a status = Returned that I need to be able to get in for North American ACHEFT processing. ACHEFT here can go from Pending -> Completed -> to Returned. And Returned is not a refund. It's also not quite a Canceled either.
  
  > **Comments:**
  > **username_3**: At a client we also had this problem. Their contributions get the status pending and then pushed to a financial system which does the sepa direct debit. This system then updates the contribution status but it wasn't allowed to do so. I have created a custom api which works around this restriction.  
  
  ---
  
  