Fatal Error with donation form on MacOS

[TheFoodDepot]

We have a donor who is currently unable to make a contribution through the donation form on this page - https://www.thefooddepot.org/covid19-crisis/.

The form is hosted here - https://thefooddepot.secure.force.co...aramfile=Covid

The OS / Browser setup is:
MacOS - 10.15.6
Safari - Version 13.1.2 (15609.3.5.1.3)
Chrome - Version 85.0.4183.83 (Official Build) (64-bit)

The form caused an error message (in the email copied below) on BOTH browsers and locked up the browser window when using Safari. The form does not appear to be causing problems on Windows.

---
Dear Customer
It appears that your last operation has caused a fatal error in our system.
Our programming team has received details of the error and will investigate
the source shortly.

You will be notified by email when the error is fixed. We apologize for any
inconvenience this might have caused and will make every effort to fix the
error as soon as possible.

Regards,

Support Department
https://www.ClickandPledge.com <https://www.clickandpledge.com/>
P: 540.961.9811, Toll Free: 866.WWW.CLICK (999.2542)
---

Your help is appreciated,
Tim Fowler

[TheFoodDepot]

I just received a call from another donor who is having a different problem with a different form. This donor has made donations in the past via the website, but now has a new PC and web browser and is seeing this error for the first time. She tried to donate multiple times and is seeing the same message each time.

Webpage - https://www.thefooddepot.org/neighborhood-donation/
Form - https://thefooddepot.secure.force.co...mfile=Neighbor
OS - Windows 10 Home - Version 1803, Build 17134.1304
Browser - Microsoft Edge - Version 85.0.564.44 (Official build) (64-bit)

Error Message -
Unexpected Error
We're sorry there has been an error in processing the transaction, please hit back on your browser and verify your information and try again.

Error Message:
Xml Error
undefined

[CnP.Support]

Good day!

We love to help but this form is in Salesforce and we have no knowledge of the underlying code. We have to login to Salesforce and review the code as well as run test transactions to determine the code issue.

Is it OK to run tests on this form?

The error you are seeing is not a FaaS error as that is not our error code. Given it is in Salesforce we have to figure out your code and run tests.

[TheFoodDepot]

Our in office Salesforce person tells me that she has granted access for testing. Hopefully that is the case.

Thanks!

[CnP.Support]

Good day!

We have reviewed the log files and see the errors posted due to invalid phone number format.

One error'd record is for: Eunice L V*******

The phone number entered is: 2267

If you pass the phone number in the form it has to match the required format. Please see: https://manual.clickandpledge.com/Fo...er_Information

If the phone number is passed the minimum length has to be 6 characters. You have the option for not sending it but if it is passed it has to match the minimum requirement.

The entries with error all have invalid phone numbers. Please add a validation to your phone field.

We are also seeing a number of invalid credit card numbers being passed. In our forms we do card validation to ensure the card number is correct - this does not mean the card will authorize but that it is a valid credit card number matching the Luhn format.

May I ask why you are doing your own form where CONNECT forms have all the fields you have in your form and has all the required validation? FaaS forms are subject to attacks if they do not have reCAPTCHA so your forms do not have any validation or security features required. Your forms are quite vulnerable.

Please consider adding validation to all your fields as well as adding a reCAPTCHA..

[TheFoodDepot]

Thanks for the answer re: invalid phone # format on the 2nd error message (Win 10 & Edge). I didn't create the form, so I can't speak to why it was setup without validation.

Is an invalid phone # format also the problem with the "Fatal Error" on MacOS and Safari OR Chrome?

Thanks

[CnP.Support]

Good day!

The browser is not the issue. If you can review the entry and then see what causes the error you will see the issue.

The error is simply due to the input not matching the API requirements as set in the manual. Please have your developer review the format requirements and set validations that match the requirements. When using an API you have to ensure that your posts match the API format requirement.

Hope that helps.