WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
INSERT INTO `wp_0vjtjby2jf_wpaas_activity_log` (`user_id`, `activity`, `timestamp`) VALUES (0, 'Fetch feature flags from API', '2024-04-30 09:43:00')

WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
ALTER TABLE wp_0vjtjby2jf_wpaas_activity_log CHANGE COLUMN `activity` activity TEXT NOT NULL

WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
INSERT INTO `wp_0vjtjby2jf_wpaas_activity_log` (`user_id`, `activity`, `timestamp`) VALUES (0, 'API call success URL: https://wp-api.wpsecurity.godaddy.com/api/v1/featureFlags/a473dc74-9e3b-11eb-8213-3417ebe60eb6 status_code: 200', '2024-04-30 09:43:00')

WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
UPDATE `wp_0vjtjby2jf_options` SET `option_value` = 'a:3:{s:11:\"account_uid\";s:36:\"a473dc74-9e3b-11eb-8213-3417ebe60eb6\";s:5:\"flags\";a:10:{i:0;a:2:{s:5:\"title\";s:21:\"smart_plugins_enabled\";s:5:\"value\";b:1;}i:1;a:2:{s:5:\"title\";s:10:\"nps_survey\";s:5:\"value\";b:1;}i:2;a:2:{s:5:\"title\";s:11:\"gmv_monitor\";s:5:\"value\";b:1;}i:3;a:2:{s:5:\"title\";s:13:\"wp643_zip_fix\";s:5:\"value\";b:1;}i:4;a:2:{s:5:\"title\";s:17:\"fullstory_wpadmin\";s:5:\"value\";b:1;}i:5;a:2:{s:5:\"title\";s:13:\"expert_banner\";s:5:\"value\";b:1;}i:6;a:2:{s:5:\"title\";s:23:\"persist-autodraft-posts\";s:5:\"value\";b:1;}i:7;a:2:{s:5:\"title\";s:26:\"wpex-3258-post-publish-CTA\";s:5:\"value\";b:1;}i:8;a:2:{s:5:\"title\";s:22:\"cta_interview_wp_admin\";s:5:\"value\";b:0;}i:9;a:2:{s:5:\"title\";s:18:\"traffic_data_admin\";s:5:\"value\";b:1;}}s:9:\"timestamp\";i:1714470180;}' WHERE `option_name` = 'wpaas_feature_flag_a473dc74-9e3b-11eb-8213-3417ebe60eb6'

WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
INSERT INTO `wp_0vjtjby2jf_wpaas_activity_log` (`user_id`, `activity`, `timestamp`) VALUES (0, 'API call success URL: https://wp-api.wpsecurity.godaddy.com/api/v1/featureFlags/a473dc74-9e3b-11eb-8213-3417ebe60eb6 status_code: 200', '2024-04-30 09:43:00')

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
INSERT INTO wp_0vjtjby2jf_aioseo_cache SET `key` = 'wp_notices', `value` = 'a:0:{}', `expiration` = '2024-05-01 09:43:00', `created` = '2024-04-30 09:43:00', `updated` = '2024-04-30 09:43:00' ON DUPLICATE KEY UPDATE `value` = 'a:0:{}', `expiration` = '2024-05-01 09:43:00', `updated` = '2024-04-30 09:43:00' /* 1 = 1 */

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /var/www/wp-includes/class-wpdb.php:1854) in /var/www/wp-includes/rest-api/class-wp-rest-server.php on line 1831
{"id":1301,"date":"2021-11-19T20:42:00","date_gmt":"2021-11-19T20:42:00","guid":{"rendered":"https:\/\/xcaliber-solutions.com\/?p=1301"},"modified":"2022-03-22T20:45:04","modified_gmt":"2022-03-22T20:45:04","slug":"the-pros-and-cons-of-chargeback-blacklists-what-you-need-to-know","status":"publish","type":"post","link":"https:\/\/xcaliber-solutions.com\/the-pros-and-cons-of-chargeback-blacklists-what-you-need-to-know\/","title":{"rendered":"The Pros and Cons of Chargeback Blacklists: What You Need to Know"},"content":{"rendered":"\n

Every merchant knows that the dramatic growth in digital commerce has brought in its wake an equally rapid surge in the prevalence of card not present (CNP) payment fraud.<\/p>\n\n\n\n

The Crippling Costs of Chargebacks and Friendly Fraud<\/h2>\n\n\n\n
They know, too, that the process of disputing chargebacks<\/a> and trying to prevent so-called \u201cfriendly\u201d fraud is difficult, time-consuming, and expensive.<\/p>\n\n\n\n
And even if they are successful in a particular case, there is little to prevent determined and brazen customers from making repeated attempts to play the system again \u2013 biased as it is in their favor.<\/p>\n\n\n\n
So why not just blacklist those customers you suspect of this kind of activity, and effectively ban them from trying to buy from you again?<\/p>\n\n\n\n
It sounds seductively simple. But there are some significant potential problems you need to be aware of before deciding to go down this route.<\/p>\n\n\n\n

Chargeback Blacklists and Databases<\/h2>\n\n\n\n
It\u2019s possible for you as a merchant to create your own blacklist or database of problem customers by manually scrutinizing orders and reviewing chargebacks. But this is a labor-intensive and therefore expensive process, particularly for smaller businesses.<\/p>\n\n\n\n
Many merchants, therefore, choose to make use of external lists or chargeback management software<\/a>. These may focus simply on a customer\u2019s history of chargeback filings, but the more effective ones will record and analyze a number of additional data points.<\/p>\n\n\n\n

The Advantages and Disadvantages of Blacklists<\/h2>\n\n\n\n
Whatever kind of list or database you use, the main advantage is the prevention of future transactions that may be suspicious.<\/p>\n\n\n\n
But the major problem is that even the most sophisticated of these lists and databases are blunt instruments that may easily catch many of your legitimate customers, causing a damaging loss of business.<\/p>\n\n\n\n
The Evasive Tactics of the Fraudsters<\/h2>\n\n\n\n
And on a practical note, you need to be aware that fraudsters are of course only too well aware that they may be blacklisted, and are using increasingly sophisticated methods to avoid being caught.<\/p>\n\n\n\n
These may be such relatively simple techniques as the use of multiple emails and IP addresses. But they may also involve one of the numerous types of hard to detect identity theft.<\/p>\n\n\n\n
None of this means that you shouldn\u2019t use blacklists. But it does mean that they should only be used as part of a comprehensive strategy for tackling chargebacks and fraud.<\/p>\n\n\n\n
Contact Us<\/h2>\n\n\n\n
It\u2019s also crucial that you use the right kind of database, one that looks at the data points that are most relevant to your business and which acts a complement to your other chargeback\/fraud systems and protocols.<\/p>\n\n\n\n
Making the right choice can be a challenge, so if you think you may need help why not contact us here<\/a>.<\/p>\n\n\n\n
Our experts are always ready to help.<\/p>\n","protected":false},"excerpt":{"rendered":"
Every merchant knows that the dramatic growth in digital commerce has brought in its wake an equally rapid surge in the prevalence of card not present (CNP) payment fraud. The Crippling Costs of Chargebacks and Friendly Fraud They know, too, that the process of disputing chargebacks and trying to prevent so-called \u201cfriendly\u201d fraud is difficult, time-consuming, and […]<\/p>\n","protected":false},"author":2,"featured_media":1302,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_coblocks_attr":"","_coblocks_dimensions":"","_coblocks_responsive_height":"","_coblocks_accordion_ie_support":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5],"tags":[],"aioseo_notices":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/xcaliber-solutions.com\/wp-content\/uploads\/2022\/03\/xcaliber-blog-chargeback-blacklist.jpg","_links":{"self":[{"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/posts\/1301"}],"collection":[{"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/comments?post=1301"}],"version-history":[{"count":1,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/posts\/1301\/revisions"}],"predecessor-version":[{"id":1303,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/posts\/1301\/revisions\/1303"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/media\/1302"}],"wp:attachment":[{"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/media?parent=1301"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/categories?post=1301"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xcaliber-solutions.com\/wp-json\/wp\/v2\/tags?post=1301"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
DELETE FROM `wp_0vjtjby2jf_options` WHERE `option_name` = '_transient_jetpack_update_remote_package_last_query'
WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
DELETE FROM `wp_0vjtjby2jf_options` WHERE `option_name` = '_transient_timeout_jetpack_update_remote_package_last_query'
WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
UPDATE `wp_0vjtjby2jf_options` SET `option_value` = '1714470240' WHERE `option_name` = '_transient_timeout_jetpack_update_remote_package_last_query'
WordPress database error: [The MySQL server is running with the --read-only option so it cannot execute this statement]
UPDATE `wp_0vjtjby2jf_options` SET `option_value` = '1714470180' WHERE `option_name` = '_transient_jetpack_update_remote_package_last_query'

Contact Us<\/h2>\n\n\n\nIt\u2019s also crucial that you use the right kind of database, one that looks at the data points that are most relevant to your business and which acts a complement to your other chargeback\/fraud systems and protocols.<\/p>\n\n\n\n