Answers.Body: <p>Welcome to CiviCRM Stack Exchange alicedd!</p>
  
  <p>Afaik, CiviSEPA mandate information cannot easily be made available in Profiles. CiviSEPA can be made available as a payment processor on CiviCRM Contribution pages though. CiviSEPA would then create a mandate when someone uses the page</p>
  
  <p>If you want to allow constituents updating a mandate you will need to create a custom form / function. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-23T20:42:22.003Z
Answers.Text: Thank you for your fast answer! It helped me a lot
Answers.UserDisplayName: alicedd
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-21T07:02:46.177Z
Answers.LastActivityDate: 2019-10-21T07:02:46.177Z
Answers.UserDisplayName: Fabian
Body: <p>I'm trying to connect the payment attributes of my wordpress/civi profiles with civisepa, so that mandates will automatically be updated if a user changes his IBAN, etc. Is there any way to achieve this?</p>
  
  <p>Thanks in advance!</p>
  
Tags: <profile><civisepa><civibanking>
Title: Is there a way to connect the civisepa backend to the profiling in wordpress?
ThreadText: # Is there a way to connect the civisepa backend to the profiling in wordpress?
  
  (Asked by: username_0 on 2019-10-19)
  
  I'm trying to connect the payment attributes of my wordpress/civi profiles with civisepa, so that mandates will automatically be updated if a user changes his IBAN, etc. Is there any way to achieve this?
  
  Thanks in advance!
  
  **Tags:** profile, civisepa, civibanking
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-10-21. Score: 1 | Accepted answer
  
  Welcome to CiviCRM Stack Exchange username_0!
  
  Afaik, CiviSEPA mandate information cannot easily be made available in Profiles. CiviSEPA can be made available as a payment processor on CiviCRM Contribution pages though. CiviSEPA would then create a mandate when someone uses the page
  
  If you want to allow constituents updating a mandate you will need to create a custom form / function.
  
  > **Comments:**
  > **username_0**: Thank you for your fast answer! It helped me a lot  
  
  ---
  
  