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 Donation forms to require fewer fields (no address required)

We are using some mobile-optimized donation forms on another platform that only require the following fields:

First Name, Last Name

Mobile Phone Number, Email

Card Number, Expiration Date, CVV

We really need to be able to have forms that don’t require:

Street, City, State, and Zip code. As we all know the more information that is required on forms (especially when viewed on mobile devices), the less likely a donor is to finish their gift.

  • Devin Gladstone
  • Mar 25 2016
  • Reviewed: Voting Open
LO - Current Gen / Existing Functionality
Area of the Product Donations
Org/Company Name Food For the Poor
  • Attach files
  • Ken Cantu commented
    July 06, 2016 16:18

     I understand, thanks!

    Ken

    ×

    Attachments Open full size

  • Devin Gladstone commented
    March 28, 2016 13:30

    Hi Ken,

    We are mainly interested in using this on mobile forms.....as this is where we believe the less fields would lead to a dramatic increase in conversions. -- Devin

    ×

    Attachments Open full size

  • Ken Cantu commented
    March 25, 2016 21:46

    Hi Devin,

    My understanding is that this is possible in current LO  however it is a business decision the organization makes on how strict or lenient they want to be on requiring fields on their transaction forms. The more lenient they are the more they have the potential to get slapped with fees from fraudulent charges from their processor however that may be less than they get from the decrease in abandonment rate because of the fewer fields. This is, however, a global site option and not set form by form.

     Is the ability to have certain forms be less strict then others what you are asking for? Or will this global option meet your needs?


    Here is the  SDP to look into for changing this globally on their site. Support can change this for you:

    PAYMENT_AVS_MATCH_LEVEL:
    The AVS services will send back one of four responses. Three of these responses can be interpreted as success. These are

    1. Exact match - The street address and ZIP code the user provided with the card number exactly match what the issuing bank has on record
    2. Street address match - The street address the user provided with the card number matches what the issuing bank has on record. The ZIP code did not match
    3. ZIP code match - The ZIP code the user provided with the card number matches what the issuing bank has on record. The street address did not match.
    4. No match - None of the billing information the user provided with the card number matches what the issuing bank has on record.

    PAYMENT_AVS_MATCH_LEVEL Controls how each of response 1, 2, 3 above will be interpreted. Valid values are

    1. FULL - Only exact matches will be marked as successful
    2. PARTIAL_STREET - Street address matches will be marked as successful
    3. PARTIAL_ZIP - ZIP code matches will be marked as successful
    4. PARTIAL - Both street address and ZIP code partial matches will be marked as successful

    Thanks,

    Ken

    ×

    Attachments Open full size

Related ideas

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