Credit card token is not being transferred to BBMS when using API to update credit card information

When using an API to update credit card information (card number and/or expiration date) eTapestry does not create a new token for transfer to BBPS/BBMS.
This issue has been resolved in the 7.22.0 Release on 6/5/2016. If a credit card had been updated through API before then, the cardholder will need to update their card again in order for the token to be created.

Steps to Duplicate

1. Donor logs into their profile using a secure PIN and updates credit card for the pledge. 
2. New credit card information is not tokenizing into BBMS.  It is remaining as the old token.
3. When eTapestry then attempts to charge the card it is rejected

Environment

 Chrome
 50
 Windows 7 (64-bit)
 eTapestry
 BBMS

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.