> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Your Activity Log Shows New Payment-Info Edits (and a Different-Looking Bank Account) After a Platform Migration

> After your organization migrates recurring donors into WeGive via a token-transfer migration, a donor's activity log can show new payment-method edits, or a bank/card number that looks different -- this is expected: migration creates a new payment-method record for the same underlying account, it does not change what a donor is charged.

## Overview

If your organization recently migrated recurring donors into WeGive from
another platform, you may notice a donor's activity log shows one or
more "payment method added" or "payment method updated" entries around
the migration date, or that a bank account number on file looks
different than what the donor remembers giving you. This is expected
behavior for this type of migration, not a sign of an error or unwanted
change to the donor's giving.

## Why this happens

When recurring donors are migrated into WeGive using a token-transfer
migration, WeGive creates a new payment-method record for each
migrated card or bank account and attaches it to the donor's existing
recurring plan. The plan itself — its amount, schedule, and giving
history — is preserved exactly as it was; only the underlying
payment-method record is new. That new record is what shows up as a
payment-info change in the donor's activity log, even though nothing
about what the donor is being charged has changed.

Because this process can create a payment-method record per recurring
plan, a donor with several recurring plans tied to the very same card or
bank account may end up with more than one payment-method entry listed
on their account after the migration — these are genuine, independent
records that each continue to charge correctly for their own plan, not
duplicates created in error.

## Why the bank account or card number can look different

The number displayed for a migrated payment method is populated from
the information provided at the time of migration, and in some cases
that stored number can differ slightly from what the donor sees on
their own bank or card statement for that account. This does not mean
the donor is being charged against the wrong account — the underlying,
functioning payment token is tied to their real account regardless of
what's displayed. If a donor reports that the displayed number truly
doesn't match any account they recognize at all (not just a formatting
or display difference), reach out to your account team so it can be
investigated further on the processor side.

## What to tell a donor who asks about this

* Their recurring gift continued (or will continue) on the same amount
  and schedule as before the migration — nothing about what they're
  charged has changed.
* The "payment method added/updated" entries in their activity log
  reflect how their existing card or bank account was brought into
  WeGive's system during the migration, not a change they need to take
  any action on.
* If they have more than one payment method listed that looks like a
  duplicate, those are typically separate records tied to separate
  recurring gifts rather than an error — no action is needed on their
  part.

## Related

* [Setting Up a Recurring Plan](/external/support/giving/setting-up-a-recurring-plan)
* [When Donors Migrate via the Semi-Automated Approach (No Token Transfer)](/external/support/portal/when-donors-migrate-via-the-semi-automated-approach-no-token-transfer)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.