form validation, error messages, and transaction fees

[ss57]

I read one other forum post (thread 1287) that stated that C&P doesn't validate form data except for empty required fields. Is this also true for field length? In other words, if someone types an email address that is 55 characters long, what happens? Is it silently truncated?

Is it still true that no data validation is performed by C&P?

Along these same lines, at what point is the data submitted to the card processor? I understand that the processing fee is charged every time a transaction hits the processor. For instance, if a required field is omitted, is this caught before being sent to the processor, thus avoiding the transaction fee?

[CnP.Support]

Good day!

I am not sure what you mean by "Form Validation" not performed by Click & Pledge? How can this possibly be the case?

The forms that are hosted at Click & Pledge, easy, advanced, friendly, Connect forms, and any forms created by us has 100% validation on all forms. Form validation is a client feature and not a server feature, meaning validation has to be done at the client. If a FaaS form or an API form is created by you then you have to have the validation yourself on the form. When you post the data to Click & Pledge the API will review the entries and post back to you in case of error with the error message and if it validates against the API schema then it will process.

You need to add the form validations and length test yourself. No server can validate this for you. It is a local form and all validation has to be local.

If a required form which is mandated by the API is not provided then the API will return an ERROR. If a charge is declined it means it has gone to the gateway and the response will be DECLINE. Error will only occur if the required fields are not posted per requirements.

I hope I have answered your question. Please let me know if we can be of any further assistance.

[ss57]

Yes, I think you have answered my question. Let me restate just to be sure.

When data is sent from a web form to the FaaS API, the data is checked against field length limits. If any problems are found, an ERROR response will be returned and no transaction fee will be charged. If no problems are found, the data will be forwarded to the gateway for processing. If a problem is found at the gateway, a DECLINE will be returned and a transaction fee will be charged.

So, is it correct that the only data check that the FaaS API performs is field length?

[CnP.Support]

Good day!

The fees are ONLY charged when we post to the gateway.

For a transaction to be posted to the gateway it has to match the gateway requirements and our error checking will catch any issues that may conflict with the gateway.

We don't just do error checking on the length - validation is on length and data type, e.g. posting a text to a numeric field will be invalid.

I hope that helps.

Please let me know if I can be of any further assistance.