updateRecurringCreditCardInfo API Questions

Error code 612001 translates to "No recurring gift found" according to the error codes page:

http://open.convio.com/api/#main.error_codes.html



Most likely, this does mean that constituents (donors) cannot update a "COMPLETED" or "CANCELLED" recurring gift, but only active/ongoing recurring gifts. If you run into a situation where a constituent would want to update a completed/cancelled recurring gift, the easiest solution is to direct the constituent to a donation form, where they can make a new recurring gift with the appropriate updated information.



You might verify a few things to confirm this issue:

1) Does the recurring_gift_id you are sending in the "updateRecurringCreditCardInfo" call match a recurring_gift_id returned by a "getRecurringGifts" call?

2) Are you submitting the "updateRecurringCreditCardInfo" with an authentication token identifying the logged-in user that made the original donation, or with valid API administrator credentials (for Server API calls) and passing the cons_id of the user that made the original donation?



For the second question, the "password" input type is only different from the "text" input type in the display to the user in their browser - the "password" input type automatically masks the characters typed by the user with asterisks or circles, while the "text" input type shows the user what they have typed. However, the value entered by the user is still accessed the same way by JavaScript, so your form submission should treat a "password" input type exactly as it would treat a "text" input type.



For example, if I have the following two fields on a form:

<input type="text" id="my_text_field">

<input type="password" id="my_password_field">

These will appear as two text input fields, with the difference that the user will see asterisks or circles when they type in the second field, rather than the text that they typed (which they would see in the first field). JavaScript, however, can access the values typed by the user in each of these fields directly. So, if I typed "12345" in each of the fields shown in my example above, I would expect to see "12345" as the "value" property of those fields in JavaScript, such as:

<script type="text/javascript">

var textValue = document.getElementById('my_text_field').value;

var passValue = document.getElementById('my_password_field').value;

if (textValue == passValue) console.log("All values are the same");

</script>

You can also see this with jQuery, or by using Web Developer tools in your browser to inspect the "POST" arguments sent in your API call. In general, any POST form submission will send the value typed by the user into a "password" input field, just as it does for "text" input fields.



I hope that helps!