Announcement

Collapse
No announcement yet.

FaaS Test Mode Bug with Credit Card Year

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • FaaS Test Mode Bug with Credit Card Year

    Hi There,

    I believe I have found a bug in the FaaS. I set up a form in test mode, which worked fine for me. I then put the webpage out for testing and several people indicated that they received failure messages. After some time investigating I discovered that if I used a credit card expiration date other than 2011, the transaction failed! I assume this is a bug - and that it only effects test mode. I'm going "live" with the site tomorrow and this will be my first time using Click and Pledge.

    The FaaS service is pretty slick, by the way.

  • #2
    David,

    I doubt if that problem is with the system since FaaS is being used by a lot of sites. Please see what value you are posting to us for the year in question. In test setting any future date should work.

    What is your site's address so we review the site and find out what is going on.
    Regards,
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      I am posting a two digit number as the year. If I use 2011 as a year, posting a value of 11, the transaction is accepted. If I use 2012 or 2013, posting 12 or 13, the transaction is denied.

      The site is presently password protected. Please see my e-mail to [email protected] for login information.

      Comment


      • #4
        Is your site public? can I see the site?
        Regards,
        Click & Pledge Support Department

        On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

        Join us @ the educational webinars: https://clickandpledge.com/webinars/
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

        Comment


        • #5
          Please do. It's password protected right now. I sent the login information via e-mail. But it's not sensitive. Go to testsite.rabbitrr.org. Username is xxx and password is xxx. Go to the Participate-Donate page.
          Last edited by David Brown; 03-31-2011, 04:47 PM.

          Comment


          • #6
            David,

            are you sure the issue is related to the Year? You are passing single digit months as 1,2,3, 4.. they need to be passed as: 01, 02, 03, 04
            Regards,
            Click & Pledge Support Department

            On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

            Join us @ the educational webinars: https://clickandpledge.com/webinars/
            Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
            Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

            Comment


            • #7
              David,

              Just tested it ..

              If I choose January 2014 it declines
              If I choose October 2014 it authorizes

              as I said in the last post the issue is the month not the year. Please change the month values to 01, 02, 03... 09 and let's test again.

              I think that will solve the problem.
              Regards,
              Click & Pledge Support Department

              On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

              Join us @ the educational webinars: https://clickandpledge.com/webinars/
              Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
              Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

              Comment


              • #8
                David,

                One more thing for you to also know when checking these messages. Please see the URL when you are directed to the error page:

                ExpirationDate'%20element%20is%20invalid%20-%20The%20value%20'1/14'%20is%20invalid%20according%20to%20its%20dataty pe%20'String'%20-%20The%20Pattern%20constraint%20failed.&RefID=

                If I remove the %20's from the URL this is what I get:

                http://www.testsite.rabbitrr.org/don...or.html?on=Xml Error The 'urn:APISchema.xsd:ExpirationDate' element is invalid - The value '1/14' is invalid according to its datatype 'String' - The Pattern constraint failed.&RefID=

                as you see the ERROR message is telling you exactly what is wrong.

                1/14 is invalid.

                It should be 01/14

                hope that helps.
                Regards,
                Click & Pledge Support Department

                On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

                Join us @ the educational webinars: https://clickandpledge.com/webinars/
                Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
                Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

                Comment


                • #9
                  Well, that's embarrassing! Yes, fixing the value posted for the month fixed the problem. And I read the FaaS Manual, I really did... I guess I missed that one.

                  I really appreciate the timely and thorough response. I am switching to Click and Pledge from Network for Good, and have been very impressed with you guys!

                  Thank you very much.

                  Comment


                  • #10
                    Thanks for the tip on the error message being embedded in the URL - that will be useful.

                    Comment

                    Working...
                    X