Stop credit card updater from changing card data on historical pay-cash gifts

Currently when card details are updated by the CCU in BBMS, the changes are pushed through to all of the old pay-cash gifts associated with that card, as well as the Recurring Gift. This is incorrect and bad for data integrity, troubleshooting and reconciliation. What's more, the card information for the corresponding transactions in BBMS is NOT changed, meaning that BBMS and RE gifts no longer match on card last four/expiry date.


We need BB to support accurate data in RE.


We need a way to match gifts in RE with transactions in BBMS so they can be reconciled. As BB have not supplied any unique identifier that can be exported from both BBMS and RE (the transaction ID is not available to be exported from RE), we rely on a combination of the authorisation code and card last four to match gifts. If the card last four are incorrect, we can't reconcile BBMS efficiently.


Please ensure CCU card updates are only pushed through to Recurring Gifts and NEW pay-cash gifts, not historical data.

  • Jenny Mulcock
  • Feb 13 2024
  • Attach files
  • Devan Caton commented
    16 May 13:40

    Agreed! Historical gift records should never be modified. I already spoke with BB Support about it. They said it's functioning as designed. It's because the payment method is tokenized and the token is associated with the Recurring Gift as well as the Pay-Cash records. I countered that I understand this but it is a flawed design. I consider this a defect/bug, but they just directed me to put it in the idea bank. Disappointing.