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.

Allow way to test event registration with payment without using personal credit card

I hate to publish an event registration page that requires payment without going completely through the registration process and  confirming functionality is working correctly. However, if I want to test this currently in Luminate, I have to charge my personal credit card and then refund the registration fee. If I have to perform multiple tests, this results in a lot of transactions on my credit card and potential of my personal funds not being available to me for several days due to time it takes for refunds to be processed. In Kintera, we could test our event registrations with bogus credit card information provided by Blackbaud. We can't do this in Luminate so it seems like an instance where we've lost functionality.

  • Debbie Campbell
  • Oct 27 2016
  • Reviewed: Voting Open
Org/Company Name Lupus Foundation of America, Indiana Chapter
  • Attach files
  • Alan Gillespie commented
    1 Sep, 2017 06:50pm

    I've achieved this using test credit numbers (google it) or by adding a hidden field to the form named df_preview that doesn't end-up processing the transaction 

  • Jeremy Reynolds commented
    26 Apr, 2017 01:23pm

    Have you tried the edit workflow's "Test Drive" step?

  • Kim Ethridge commented
    1 Nov, 2016 11:23pm

    We can test this way in NetCommunity. We're moving to LO and I'm sure we're going to have the same issues. This should really be changed.

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