Credit card information is retained after the constituent is changed in Membership Dues Batch

If you change the constituent in a Membership Dues Batch, you might notice that the credit card payment information from the first constituent is retained.
This is a scenario in which the credit card would have already been tokenized. With this in mind the decision to remove the credit card information from the batch row would need to be a manual change by the CRM end user. 

Steps to Duplicate

1) Register for a membership using a credit card in BBIS and download the transaction into CRM.
2) Open the batch and take a look at the Membership details and payment information.
3) Change the constituent in the batch.
4) Notice that the membership details have cleared out but the credit card information from the original constituent remains.

Environment

 Blackbaud CRM
 4.0
 4.0.166.0

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.