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