Announcement

Collapse
No announcement yet.

FaaS has been working and now not

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

  • FaaS has been working and now not

    Hello:

    My client's FaaS has been working for a few months. It stopped working yesterday. Three different cards from three different people, and card error. Although client is still able to process through the virtual terminal.

    The URL is https://www.torgan2012.com/contribute.php

    I've checked the AccountGuid, AccountID, and the WID. All appear to be correct.

    Thanks for your help,
    Matt

  • #2
    Matt,

    The ERROR message tells you what is wrong. Have you tested this in TEST mode?

    Naturally something has changed in your account or settings that is causing the error. Please post the error message and we can figure 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
      The error message that client is receiving:


      "We're sorry, there was an error with your credit card. Please try again by clicking the back button in your browser and using a different card. If you continue to have a problem, let us know."


      Even though the same card was later correctly processed through the virtual terminal.


      And when I used the FaaS with my own card, everything worked fine. And in at least one occurrence, my client tried the transaction from within his website (which did generate the error) and then from the virtual terminal (which did not generate the error) and received two receipts with two different transaction numbers.


      And yes, before going live in production mode a few months ago, we did testing in test mode. It has been working fine from the time of going live until now. I have made no changes to my code or to the client's account (I cannot comment on whether or not the client may have inadvertently made changes to his account, but he says not).


      Thanks,
      Matt

      Comment


      • #4
        Matt,

        We have tested your form with our test account and all appear to be working fine.

        I have also tested your page with a $0.50 transaction and it went through without any issues. I also suggest that you refer to an ERROR as anything that is returned to the ERROR page and DECLINED when returned to the Decline page.

        A decline is not an ERROR.

        One suggestion for backward compatibility is to add a 1 to all your item names - see below:

        HTML Code:
        <input name="ItemID1" type="hidden" id="ItemID1" value="1">
                <input name="ItemName1" type="hidden" id="ItemName1" value="Donation">
                <input name="Quantity1" type="hidden" id="Quantity1" value="1">
                <div class="indicates-required"><span class="asterisk">*</span> indicates required</div>
                <fieldset>
                  <legend>Please choose your contribution amount:</legend>
                  <label class="amount">
                  <input type="radio" name="UnitPrice1" id="UnitPrice1" value="50" checked="checked">$50</label>
                  <label class="amount">
                  <input type="radio" name="UnitPrice1" id="UnitPrice1" value="250">$250</label>
                  <label class="amount">
                  <input type="radio" name="UnitPrice1" id="UnitPrice1" value="500">$500</label>
                  <label class="amount">
                  <input type="radio" name="UnitPrice1" id="UnitPrice1" value="1000">$1000</label>
                  <label class="amountOther">
                  <input type="radio" name="UnitPrice1" id="UnitPrice1" value="Other"> Other $
                  <input name="Other1" type="text" id="Other1" class="amountOtherfield" size="8">
                  </label>
        Using 1 as the suffix helps with future changes you may want to make. The system is backward compatible but it is good if you add a 1 as shown above.

        As stated I tested the page and nothing appears to be wrong. If a bank declines a transaction it may be best to contact and find out why it was declined.

        Let us know if you are still experiencing this problem and if an ERROR occurs please send us the detailed error message.
        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

        Working...
        X