manually_storing_credit_cards_in_system_5_in_a_non-integrated_data_set
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | manually_storing_credit_cards_in_system_5_in_a_non-integrated_data_set [2017/08/02 15:25 (7 years ago)] (current) – created sjackson | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== How to activate the " | ||
+ | |||
+ | The customer might be using a “Standalone” CC/Debit processing not integrated with System5. And, they may need to record the CC information so that they will be able to manually input it into the standalone pinpad. That’s the full credit card number, expiry and CVV. | ||
+ | |||
+ | There are few places within System5 where one might be tempted to store this information, | ||
+ | |||
+ | The only way “legal” way of storing/ | ||
+ | |||
+ | - Enable " | ||
+ | - Backup the old licence code. | ||
+ | - Backup the dataset. | ||
+ | - Install the new licence code on the customer' | ||
+ | - Explain the complex passwords needed for Users and Security settings that have a "#" | ||
+ | - Enable PCI on the customer' | ||
+ | - Make the users enter complex passwords, or remove their "#" | ||
+ | - Within the Payment Processors tab in System5, enable the option to allow users to view the full card numbers, because by default, they are always encrypted. See image below. | ||
+ | {{: | ||
manually_storing_credit_cards_in_system_5_in_a_non-integrated_data_set.txt · Last modified: 2017/08/02 15:25 (7 years ago) by sjackson