We are evaluating EchoSign to receive customer Credit Card and CVV information for payment against a contract.

[AspenskiingcompanyH]

Is EchoSign PRO appropriate as it does not support Advanced Form Fields?  Is this covered in Team or Enterprise/Global? Or is it best practice to integrate the CC data fields into our own PDF form with the idea that the data in transit is wrapped in SSL and 256BIT AES?

[Jat ATS · Accepted solution]

Hello,

An EchoSign Pro subscription will allow for field data to be masked, and setting up that property is pretty quick with the in-tool form creator.

For masking fields follow these simple steps.

1) Log in to your EchoSign account and upload the document and make sure u check the check box "Preview, position signatures or add form fields".
2) This will take you to the page where in you have to put the form fields (boxes).
3) Now click the tab that says Data fields along the top, just above the Signature block(red in color).
4) This opens the Data fields options. Select the "text field", and place it in the required place.
5) Double click on that text field, and the properties menu will open for the field.
6) Near the top of the Properties menu, you will find a check box that says Mask field data, check that box and save changes and you are good to go!

Masked field data will not be visible to any subsequent signer to the document, and will not be view-able on the final PDF.

To recover the field information, you will have to pull a CSV of the field data from the transaction. This can be done per transaction from the Manage tab in EchoSign, or from the History tab if you create a re-usable document.

For ease of use, we recommend creating the document as a reusable template as the History tab export will give you a full history every time.

One thing to note with Credit Card numbers is that you want to break the field of 16 numbers into two fields.

Opening a CSV in Excel will truncate a field number to 15 significant numbers, and you want all 16.

Please see this article for a more information.

[ktotheb]

Last I checked, EchoSign downloads a temp Excel doc in order to reveal the masked data, which is not PCI Compliant. Have there been any improvements or changes with how masked data is viewed with Adobe DC? Or is it EchoSign rebanded?