Answers.Body: <blockquote>
    <p>To generate these required Sepa mandate reference codes I thought I
    could use the API SepaMandate with the create action. This API
    requires an entity table and id, which I do not have yet. </p>
  </blockquote>
  
  <p>There's currently two API calls for creating a SEPA mandate: <code>SepaMandate.create</code> and <code>SepaMandate.createfull</code>. The first one requires indeed a contribution/recurring_contribution to exist, the second one will create both in one go. Both of them take a <code>reference</code> parameter with an externally generated mandate reference number. If this is not set, a new reference number will be generated. Does that answer your question?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-12T14:58:08.047Z
Answers.Text: To be complete, I have used the API SepaMandate createfull with parameters: type=RCUR, frequence_unit=month, frequence_unit=1, amount=12.5, start_date=01-06-2015. This generates a recurring contribution AND a SEPA Mandate.
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-11T11:15:04.913Z
Answers.LastActivityDate: 2015-05-11T11:15:04.913Z
Answers.UserDisplayName: Björn Endres
Body: <p>Business logic:
  Customer sends out street walkers who recruit recurring donors on the streets with forms in their hands (or on their tablets). They need to create SEPA mandate reference numbers in advance.
  Customer has implemented the basic CiviSepa and CiviBanking extensions.
  I am going to add this functionality to the CiviSepa extension (see <a href="https://github.com/Project60/org.project60.sepa/issues/271" rel="nofollow">https://github.com/Project60/org.project60.sepa/issues/271</a>)</p>
  
  <p>To generate these required Sepa mandate reference codes I thought I could use the API SepaMandate with the create action. This API requires an entity table and id, which I do not have yet. Should I still use the API or should I set up a separate table for the generated references and use those to create a mandate once the recurring contribution is added?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-09T13:47:40.897Z
Comments.Text: Erik - The term "street walkers" has a very different meaning in the US than the way you use it.
Comments.UserDisplayName: Sarah Poger Gladstone
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-11T07:29:34.880Z
Comments.Text: Thanks @Sarah I will ask no further :-) Do you have the right word for me?
Comments.UserDisplayName: ErikH - CiviCooP
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-11T13:26:58.753Z
Comments.Text: I would suggest "sidewalk donor recruiters". Then again, it depends on your customer, and what the "donation" is meant to cover. :-)
Comments.UserDisplayName: Sarah Poger Gladstone
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-11T13:36:43.483Z
Comments.Text: As said before, I think I will leave the subject well alone :-) Thanks @Sarah!
Comments.UserDisplayName: ErikH - CiviCooP
Tags: <api><civisepa><recurring-contributions>
Title: Need to create a SepaMandate for street walkers?
ThreadText: # Need to create a SepaMandate for street walkers?
  
  (Asked by: username_0 on 2015-05-09)
  
  Business logic:
  Customer sends out street walkers who recruit recurring donors on the streets with forms in their hands (or on their tablets). They need to create SEPA mandate reference numbers in advance.
  Customer has implemented the basic CiviSepa and CiviBanking extensions.
  I am going to add this functionality to the CiviSepa extension (see <https://github.com/Project60/org.project60.sepa/issues/271>)
  
  To generate these required Sepa mandate reference codes I thought I could use the API SepaMandate with the create action. This API requires an entity table and id, which I do not have yet. Should I still use the API or should I set up a separate table for the generated references and use those to create a mandate once the recurring contribution is added?
  
  **Tags:** api, civisepa, recurring-contributions
  
  > **Comments:**
  > **username_1**: Erik - The term "street walkers" has a very different meaning in the US than the way you use it.  
  > **username_0**: Thanks @Sarah I will ask no further :-) Do you have the right word for me?  
  > **username_1**: I would suggest "sidewalk donor recruiters". Then again, it depends on your customer, and what the "donation" is meant to cover. :-)  
  > **username_0**: As said before, I think I will leave the subject well alone :-) Thanks @Sarah!  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2015-05-11. Score: 3 | Accepted answer
  
  > To generate these required Sepa mandate reference codes I thought I
  > could use the API SepaMandate with the create action. This API
  > requires an entity table and id, which I do not have yet.
  
  There's currently two API calls for creating a SEPA mandate: `SepaMandate.create` and `SepaMandate.createfull`. The first one requires indeed a contribution/recurring\_contribution to exist, the second one will create both in one go. Both of them take a `reference` parameter with an externally generated mandate reference number. If this is not set, a new reference number will be generated. Does that answer your question?
  
  > **Comments:**
  > **username_0**: To be complete, I have used the API SepaMandate createfull with parameters: type=RCUR, frequence_unit=month, frequence_unit=1, amount=12.5, start_date=01-06-2015. This generates a recurring contribution AND a SEPA Mandate.  
  
  ---
  
  