I believe that the agreement governing these retail card machines is very specific regarding how the data can be stored. I am sure that your client will violate their consent to use this machine if they do what you described.
If you are not actually processing transactions yourself, I do not know that you should be a PCI complaint. This is a voluntary industry standard, not a law. Of course, if you do not follow it, you are not allowed to participate in the long-term storage of customer information if you want to do business in the payment card industry ...
Ask for a copy of your client terminal agreement. I am sure that he says very specific things about the electronic storage of customer information.
This is a really bad idea. The obligations associated with this are enormous (millions of dollars, if you have a small-scale breach, as a rule). PCI approval will cost you at least $ 50k, probably a lot more, especially if you don't have a team that previously had embedded systems.
You need to find an existing processor that provides a remote data warehouse for your client. Providers I have worked with in the past have included MyBillingTree.com and Profitstars . The latter is a larger, more professional outfit, but they are still reselling someone else api. Any major provider of enterprise payment solutions should have this opportunity. Do not go with PayPal, they are usually overrated and have limited flexibility. If your volumes are not ridiculously low, any of these companies will indicate a competitive rate to you, possibly much better than the saber-terminal that your client already has.
You do not have to perform authorization and capture delays. With the profitstars API, you can start the pre-authorizer, return the saved token representing a set of customer information, and (provided that you have the correct client authorization), use this to start transactions for arbitrary amounts later.
source share