I am curious - does the lookup to match happen AS the donor is filling out the donation form or AFTER it is submitted? Depending on the answer to this, I can think of multiple conditional search options or, alternatively, predictive possibilities that would make this duplicate creation business all go away! EVEN IF the same email lives on two separate profiles and types of profiles.

I too love Mary Cummings' idea! I also want to emphasize the need for a tribute review in this process as well. When various donors identify different people to be notified of a tribute gift, we are currently unable to to link the individual donation to the 'to be notified' entered. They all get grouped together under a single tribute.

Here's some additional info for Valerie and others whose databases are organized with donor households. We've learned that, if you merge the stripe created, 'individual record' into the household, the next time that same donor makes a Stripe gift, Stripe-Csuite will generate another duplicate, individual record. The only way to avoid this is to add the Stripe-created, individual record to an existing household.

We've also learned the one way to prevent future Stripe-created duplicates (when donors who are part of a household make a first time, Stripe gift) is to create a 'trifecta' within your households, so that every household has 3 'individual' members - ptr/spouse1 + ptr/spouse2 + ptr-spouse1/ptr-spouse2. Something to talk with your CSM about.

I agree with this and also the auto add of county to address 2 line is not wanted

I concur with both Mary Cummings' suggestion AND with Kathy Pope's suggestion to have a bucket of Stripe transactions that do NOT post automatically and can be matched or linked to appropriate existing donors and/or Tributes.

I like Mary Cummings Idea below

Another thought: what about creating a "bucket" where online donations arrive from Stripe allowing the user to process them by either matching them to existing profiles in CSuite or creating a new profile. This step would be appreciated for associated tributes as well.

I also would like the Stripe donations to be put in a "bucket" so we can make sure the donation is put to the correct endowment fund. I prefer that the online donations do not automatically post to the general ledger.

I came to idea lab specifically to look for info on this thread...
We are having the same problem of duplicates and creation of individual vs. household profiles. I would love to see "household" added as an option for the donor to choose on the checkout page, instead of just indiv or org. Most of my time has been spent converting indiv profiles to households and merging into existing profiles. Hope we see a solution soon!

NEW INFO and additional recommendation:
CSuite's Stripe transaction recording process does not recognize Household profiles; it can only match individual profiles. As a result, if your donor data is organized into households, and you don't have individual profiles created for each household member, Stripe will automatically create a duplicate, even if name, email address and phone match. The more concerning issue is that a large number of these duplicates are not detected by Stripe's duplicate finder. The only way to identify and correct the duplicates is to investigate every Stripe-created profile that doesn't have a legacy code. In December, out of 457 Stripe-generated profiles, we found 229 duplicates created because we did not have individual profiles within our households, and most of the duplicates did not appear on the Stripe duplicates list.

Recommend Foundant adopt processes to ensure that, if a user’s data will be organized into households, individual profiles for each member (as well as for both household members, together) are created for each household.

A small change that would at least decrease the work associated with merging these stripe duplicates would be to allow people to donate as a Household. Currently, the only choices are Individual and Organization, so we first have to change an "individual" (people will enter Joe and Sue Smith as an Individual) and then we have to merge it to the existing Household profile.

Another thought: what about creating a "bucket" where online donations arrive from Stripe allowing the user to process them by either matching them to existing profiles in CSuite or creating a new profile. This step would be appreciated for associated tributes as well.

Having worked in various donor databases, I would amend this idea. Every donor database has this issue because of a lack of a unique ID. Make the parameters two strict and it is difficult for donors to complete the trx. We prefer it this way and live with the work coming in the form of regular deduping. I think a good in between would be the ability for each org to set their matching parameters, but that is without knowing how Stripe works.

Yes!!! Happy to vote for this one. Please see what you can do to fix/decrease this.

I don't have the problem of deleting the gift because when we merge the profiles the gift info sticks to the cleaned up profile. I do however have a large number of duplicate profiles created with Stripe or free ticket transactions that create a large amount of work.

It would be nice if profiles were id'd by their emails. This would stop most of this duplicate situation and this is how most CRM's operate.

Thanks for the feedback Jessica. Our duplication rate is approximately 90%. Foundant, please consider: 1) allowing us to choose to allow Stripe gifts to not auto-post, or 2) not deleting a stripe gift when we need to unpost it to change the fund. That way we can edit the fund without having to re-create the entire gift.

Instead of unposting and deleting the Stripe payment and donation, we simply merge the new profile with an existing profile. This keeps all transactions associated with either profile in the single newly merged profile. There is no need to change the donor profile on the payment if all you need to accomplish is merging duplicate profiles. However, if you need to change the donor profile on the payment for another reason, this can be accomplished. When on the Profile Payment screen, you can simply click "edit" beside the Profile and select a different profile. This allows you to change the donor profile without having to unpost or delete anything. I agree that Stripe payments create many duplicates but if the donor puts in matching information to what CSuite already has recorded in a profile, the system will not create a duplicate. If they're using a different phone number or email address, though, the system will create a new profile. We just keep an eye on the duplicate profiles section of CSuite to help us merge profiles. It isn't perfect, but it is helpful. Hope this helps!

When a person donates via Stripe, the system ALWAYS creates a new profile for that person. It is extremely time consuming to unpost (and delete) that Stripe payment and donation, merge the newly created profile with the existing one, and re-enter the payment/donation. We loose all the stripe transaction data too. If the system would simply not auto post Stripe donations, AND allow us to change the donor profile on the payment, this would make a huge difference!