X-Payments:General settings - Revision history

Dohtur at 10:34, 2 December 2019

2019-12-02T10:34:32Z

Dohtur: /* Payments */

2019-11-21T06:31:15Z

‎Payments

Dohtur: /* Proxy */

2019-04-29T11:10:47Z

‎Proxy

Dohtur: /* Proxy */

2019-04-29T11:05:14Z

‎Proxy

Dohtur at 10:59, 29 April 2019

2019-04-29T10:59:57Z

Dohtur at 09:18, 29 April 2019

2019-04-29T09:18:29Z

Dohtur: /* Payments */

2019-04-29T06:48:41Z

‎Payments

Dohtur at 06:47, 29 April 2019

2019-04-29T06:47:58Z

Dohtur at 06:19, 29 April 2019

2019-04-29T06:19:32Z

Dohtur: /* General settings */

2019-04-29T06:12:19Z

‎General settings

← Older revision		Revision as of 10:34, 2 December 2019
Line 1:		Line 1:
	<noinclude>{{XP_manual_TOC}}</noinclude>		<noinclude>{{XP_manual_TOC}}</noinclude>
		+
		+	__NOTOC__<br>

	The settings that control the operation of X-Payments in general can be found on the 'General settings' page (Settings -> General settings). After adjusting any settings on this page, be sure to click '''Save''' to save the changes.		The settings that control the operation of X-Payments in general can be found on the 'General settings' page (Settings -> General settings). After adjusting any settings on this page, be sure to click '''Save''' to save the changes.

@@ Line 22: / Line 22: @@
 :[[File:XP_payments_settings.png|border]]
-* '''Maximum allowed payment attempts''': Specify how many attempts a customer should be given to submit their payment card details that are being declined by a gateway before their order is considered declined. This setting allows you to set a limit on the number of credit card entry attempts to prevent potential attempts at spam and guessing the credit card details by fraudsters.
+* '''Maximum allowed payment attempts''': This setting is available in X-Payments versions 3.1.2 and later. It enables you to set a limit on the number of payment card information entry attempts that should be available to a user within a single payment session. This feature is aimed at preventing fraudsters from using other people's payment information by guessing it and making repetitive attempts to submit it as their own. The number specified in this field will be treated as the number of attempts a user should be given to submit their payment information to the payment gateway. For example, if you set this number to "1", users will be able to submit their payment information just once per payment session. If the payment attempt fails (for example, because the payment information being used is incorrect), the order will be declined. Or, for example, if this number is set to "3", and a user's first payment attempt is rejected by the payment gateway, the user will be able to update their payment information and try again two more times. After all the payment attempts - as allowed by this setting - have been used, the user's order will be declined.
 * '''Display "Save card" option enabled by default''': When a payment configuration with tokenization support is used for payment, a checkbox option to save the credit card ("I want to use this credit card for my future orders in this shop") is provided below the credit card entry form. The setting "Display "Save card" option enabled by default" enables you to set the default state of that checkbox.

@@ Line 65: / Line 65: @@
 This section allows you to manage your proxy related settings.
-:[[File:XP_proxy_settings.png|border]]
+:[[File:XP_cloudflare_settings.png|border]]
 * '''Enable Cloudflare support''': If your store server uses Cloudflare, it may interfere with the work of X-Payments. You may want to enable this option to resolve the IP address related issues that may arise if using Cloudflare.

@@ Line 65: / Line 65: @@
 This section allows you to manage your proxy related settings.
-:[[File:XP_proxy_settings.png]]
+:[[File:XP_proxy_settings.png|border]]
 * '''Enable Cloudflare support''': If your store server uses Cloudflare, it may interfere with the work of X-Payments. You may want to enable this option to resolve the IP address related issues that may arise if using Cloudflare.

@@ Line 6: / Line 6: @@
 : [[File:XP_general_settings.png|border]]
-* '''Current time and date''': Specify the current time and date.
+* '''Current time and date''': Specify the current time and date (This is needed so X-Payments can record the time and date of payments correctly).
 * '''User account password lifetime (days)''': This setting applies to all X-Payments users except for the root administrator; it ensures that X-Payments users will regularly change their account passwords. Here you must enter the number of days that user account passwords will be valid for. Users will be supposed to change their account password before the period defined by this setting expires for their account; otherwise, the account will be locked, after which only the X-Payments root administrator will be able to unlock it. It is possible to enable email notifications for users whose account is about to be locked due to password expiration (See the 'Account is locked due to password expiration' setting in 'General settings/Email Notifications').
@@ Line 16: / Line 16: @@
 * '''Show errors on the Dashboard page for the last X days''': Specify the number of days for which you want transaction errors to be displayed on the Dashboard.
-* '''Remove log files after X days''': Specify how long X-Payments log files should be stored before removal. Note that log files should be stored for at least 90 days.
+* '''Remove log files after X days''': Specify how long X-Payments log files should be stored before removal. Note that according to PCI DSS requirements log files must be stored for at least 90 days.
 ===Payments===
@@ Line 22: / Line 22: @@
 :[[File:XP_payments_settings.png|border]]
-* '''Maximum allowed payment attempts''': Specify how many attempts a customer should be given to submit their payment card details that are being declined by a gateway before their order is considered declined.
+* '''Maximum allowed payment attempts''': Specify how many attempts a customer should be given to submit their payment card details that are being declined by a gateway before their order is considered declined. This setting allows you to set a limit on the number of credit card entry attempts to prevent potential attempts at spam and guessing the credit card details by fraudsters.
 * '''Display "Save card" option enabled by default''': When a payment configuration with tokenization support is used for payment, a checkbox option to save the credit card ("I want to use this credit card for my future orders in this shop") is provided below the credit card entry form. The setting "Display "Save card" option enabled by default" enables you to set the default state of that checkbox.
@@ Line 60: / Line 60: @@
 : [[File:XP2.0_event_notifs_gensettings.png|border]]
-Use the check boxes in the 'User account email' column to select notifications for owners of X-Payments user accounts, the check boxes in the 'User management email' column - notifications for owner of the User management notifications email address.
+Use the checkboxes in the 'User account email' column to select notifications for owners of X-Payments user accounts, the checkboxes in the 'User management email' column - notifications for owner of the User management notifications email address.
 <noinclude>{{pdf_single}}</noinclude>
 [[Category:X-Payments User Manual]]

@@ Line 19: / Line 19: @@
 ===Payments===
 :[[File:XP_payments_settings.png|border]]
@@ Line 27: / Line 28: @@
 ===Cardholder Data===
-: [[File:XP2.0_cardholder_data_gensettings.png|border]]
+: [[File:XP_cardholderdata_settings.png|border]]
-The settings in this section control collection and storage of cardholder data.
+The setting in this section controls the storage of cardholder data.
-Choose one of the following:
+* '''Retention period (days)''': Specify the number of days that the collected cardholder data is to be retained. Removal of stored cardholder data occurs as a result of [[X-Payments:Installation#Running_the_cron.php_script|running the cron.php script]]. When this script is run, a check is conducted to determine whether it is already time to remove the stored cardholder data. Then all instances of cardholder data that have been stored for the number of days defined by the "Retention period (days)" setting or longer are removed. If the "Retention period (days)" setting is set to "0" (zero), the data is removed at the first run of cron.php after the data has been collected.
 ===Email Notifications===

← Older revision		Revision as of 06:47, 29 April 2019
Line 17:		Line 17:

	* '''Remove log files after X days''': Specify how long X-Payments log files should be stored before removal. Note that log files should be stored for at least 90 days.		* '''Remove log files after X days''': Specify how long X-Payments log files should be stored before removal. Note that log files should be stored for at least 90 days.
		+
		+	===Payments===
		+	:[[xp_payments_settings\|border]]
		+
		+	* '''Maximum allowed payment attempts''': Specify how many attempts a customer should be given to submit their payment card details that are being declined by a gateway before their order is considered declined.
		+
		+	* '''Display "Save card" option enabled by default''': When a payment configuration with tokenization support is used for payment, a checkbox option to save the credit card ("I want to use this credit card for my future orders in this shop") is provided below the credit card entry form. The setting "Display "Save card" option enabled by default" enables you to set the default state of that checkbox.

	===Cardholder Data===		===Cardholder Data===

@@ Line 4: / Line 4: @@
 ===General settings===
-: [[File:XP2.0_general_settings.png|border]]
+: [[File:XP_general_settings.png|border]]
 * '''User account password lifetime (days)''': This setting applies to all X-Payments users except for the root administrator; it ensures that X-Payments users will regularly change their account passwords. Here you must enter the number of days that user account passwords will be valid for. Users will be supposed to change their account password before the period defined by this setting expires for their account; otherwise the account will be locked, after which only the X-Payments root administrator will be able to unlock it. It is possible to enable email notifications for users whose account is about to be locked due to password expiration (See the 'Account is locked due to password expiration' setting in 'General settings/Email Notifications').