Welcome to Luminate Ideas!

Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.

If you believe you are experiencing a defect please contact Support.

Do not create an active constituent record when it results from failed transaction

In order to determine if a transaction is fraudulent, LO first has to create a constituent record so the information can be sent to the merchant account. I propose making a product change so that the system not create an *active* constituent record.

Why? Active constituent records sync over to other database systems (offline CRM, mobile vendor, etc.) AND active constituent records receive email. When the data is bad, such as via a carding run, it takes staff time to identify said records, and then remove/clean the data across mulitple systems. If not addressed, it can have negative downstream effects, such as impacting email deliverability and inflating direct mail costs.

This issue impacts organizations large and small. Large organizations sometimes are able to dedicate the resources to clean the data; small most often are not. 

  • Guest
  • Sep 3 2019
  • Planned
LO - Current Gen / Pain point
Area of the Product Database
Org/Company Name World Wildlife Fund

Related ideas

Privacy Policy | Safe Harbor Notice | Terms of Use | Acceptable Use Policy | © 2019 Blackbaud, Inc. All Rights Reserved