You are viewing limited content. For full access, please sign in.

Question

Question

Input Forms Payment Gateway Information Using A Credit Card Reader

asked on March 16, 2020

Has anyone had success in using a credit card reader to input the information in Forms Payment Gateway?  Is it possible using a script or using Connector and 3rd party card reader application?

0 0

Answer

SELECTED ANSWER
replied on March 30, 2020

Laserfiche has pointed out a card reader can not be used with Forms out of the box.  Even if it could be done with an integration, the credit card and payment information would be stored in the Forms database.  Laserfiche isn’t PCI compliant at this time.

0 0
replied on December 7, 2020

Hi Barry, I was wondering if you have any additional documentation and/or information on this? I thought that using a PCI compliant payment gateway kept card information out of the Forms database. Why would using a card reader to send card information to a LF payment gateway cause Forms to store the data? 

 Maybe I misunderstood your post?

0 0
replied on December 10, 2020

Chelsey,

I don't have any further information on this issue.  My guess is the card read would have to pass the data to Forms.  So Forms would have to save the data as a value in the SQL database to use it.  The passed data would not be transmitted and/or saved using encryption.  Since Forms isn't written to do that, the data would be saved in Forms as plain text.

0 0
replied on December 10, 2020

Hmm ok. Thanks for the follow up. I don't know how we will be able to maintain PCI compliance using the Forms payment gateway if we can't use a card reader. Seems odd that this hasn't been accounted for? I wonder if other agencies are not able to implement the Forms payment gateway for this reason.

Anyways, thanks for the information! Your posts across the LF Answers forum have helped me out several times! smiley

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.