[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fiPL2TFukuJIlnuGOSFFGAViQ0pGKDTxhT9WCTmMI3Do":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":23,"download_link":24,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":36,"analysis":144,"fingerprints":225},"numly-numbers","numly Numbers","2.6","Scott Grayban","https:\u002F\u002Fprofiles.wordpress.org\u002Fsgrayban\u002F","\u003Cp>numly Numbers was born from a very old plugin called wp-numly which was originally called wp-esbn that was\u003Cbr \u002F>\ncoded by Cal Evans. But over the years his plugin stopped working and he no longer worked on it. I took the\u003Cbr \u002F>\nold plugin and chopped out what wasn’t needed and fixed what was broken which gave birth to numly Numbers.\u003C\u002Fp>\n\u003Cp>Electronic Standard Number (numly) is the unique identifier of electronic content and media. numlys are\u003Cbr \u002F>\nrecognized worldwide by electronic publishing companies and electronic content providers. They serve as branded\u003Cbr \u002F>\nidentifier or copyright for individuals or companies developing electronic content and media. numlys are\u003Cbr \u002F>\nassigned and managed by \u003Ca href=\"http:\u002F\u002Fwww.numly.com\" rel=\"nofollow ugc\">numly.com\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>The plugin registers your copyright with Numly and returns the Numly Number (electronic serial number), barcode,\u003Cbr \u002F>\nand verification links to your blog post automatically.\u003C\u002Fp>\n\u003Cp>I hope you enjoy numly numbers as much as I do.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>*** NOTE ***\u003C\u002Fstrong> You must have a active subscription at \u003Ca href=\"http:\u002F\u002Fwww.numly.com\" rel=\"nofollow ugc\">numly.com\u003C\u002Fa> for this addon to work.\u003C\u002Fp>\n\u003Cp>If you like this plugin please \u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fcgi-bin\u002Fwebscr?cmd=_s-xclick&hosted_button_id=NAL594NVVW8AU\" rel=\"nofollow ugc\">donate\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Visit our Firefox \u003Ca href=\"http:\u002F\u002Fhome.savannah.borgnet.us\u002Fnumly\u002F\" rel=\"nofollow ugc\">addon\u003C\u002Fa> for numly Numbers.\u003C\u002Fp>\n","The plugin registers your copyright with Numly and returns the Numly Number (ESN), barcode, and verification links to your blog post automatically.",10,2313,0,"2015-11-25T11:48:00.000Z","4.4.34","3.0","",[19,20,21,22],"electronic-serial-numbers","esbn","esn","numly","http:\u002F\u002Fblog.borgnet.us\u002Flinks\u002Fnumly-numbers\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnumly-numbers.2.6.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":25,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"sgrayban",2,20,30,84,"2026-04-05T17:30:43.294Z",[37,62,86,106,124],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":31,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":13,"last_vuln_date":61,"fetched_at":27},"yesno","Yes\u002FNo Chart","1.0.12","kohseiworks","https:\u002F\u002Fprofiles.wordpress.org\u002Fkohseiworks\u002F","\u003Cp>This plugin provides the function to create a set of questions to answer with “yes \u002F no (\u002For other)”. \u003Cbr \u002F>\nRequires PHP: 7.0\u003Cbr \u002F>\nYes\u002FNoチャートを作れるプラグインです。\u003Cbr \u002F>\n必須PHPバージョン：7.0\u003C\u002Fp>\n\u003Cp>The guide is here. ガイドはこちらです\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fkohsei-works.com\u002Fplugins\" rel=\"nofollow ugc\">日本語(ja)\u003C\u002Fa>\u003C\u002Fp>\n","This plugin provides the function to create a set of questions to answer with \"yes \u002F no (\u002For other)\". Yes\u002FNoチャートを作れるプラグインです。",2000,21951,90,"2026-01-06T09:05:00.000Z","6.9.4","4.4","7.0",[53,54,55,56,38],"answer","chart","question","questionnaire","https:\u002F\u002Fkohsei-works.com\u002Fplugins","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fyesno.1.0.12.zip",100,1,"2021-05-31 00:00:00",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":59,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":49,"requires_at_least":74,"requires_php":75,"tags":76,"homepage":82,"download_link":83,"security_score":84,"vuln_count":60,"unpatched_count":13,"last_vuln_date":85,"fetched_at":27},"bluesnap-payment-gateway-for-woocommerce","BlueSnap Payment Gateway for WooCommerce","3.4.1","Scott Ring","https:\u002F\u002Fprofiles.wordpress.org\u002Fbluesnap\u002F","\u003Cp>Why use the BlueSnap Payment Gateway for WooCommerce\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Accept all major debit and credit cards as well as Apple Pay, Google Pay and ACH\u003C\u002Fli>\n\u003Cli>Simplify your PCI compliance using our built-in Hosted Payment Fields. Your shoppers never leave your site while you maintain easy PCI compliance.\u003C\u002Fli>\n\u003Cli>Supports Strong Customer Authentication (SCA) with 3D Secure\u003C\u002Fli>\n\u003Cli>Identify and prevent fraud with built-in fraud protection from Kount\u003C\u002Fli>\n\u003Cli>Sell in 100 currencies \u003C\u002Fli>\n\u003Cli>Support for WooCommerce pre-orders\u003C\u002Fli>\n\u003Cli>Support recurring payments via WooCommerce Subscriptions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A secure and frictionless checkout flow\u003C\u002Fp>\n\u003Cp>The BlueSnap Payment Gateway for WooCommerce uses our Hosted Payment Fields to provide you with a seamless, PCI-compliant checkout experience that works within any browser or device.  Our Hosted Payment Fields silently collect your shopper’s sensitive payment data on BlueSnap servers without interrupting the checkout flow.\u003C\u002Fp>\n\u003Cp>Sell and settle in multiple currencies\u003C\u002Fp>\n\u003Cp>A simple way to help your shoppers complete their purchase is to offer your products in the currency of your shoppers. The BlueSnap Payment Gateway allows your shoppers to checkout in 100 different currencies and, as an added benefit, using the BlueSnap Payment Gateway gets you access to our connections to 30 global banks. When your shopper completes their purchase, BlueSnap paves the most efficient path to payment success by routing the transaction to the most appropriate local bank for your shopper, minimizing decline rates and maximizing revenue gains.\u003C\u002Fp>\n\u003Cp>Once the sale is complete and you need to get paid, BlueSnap works with you by offering the option to get money into your account in one of our 17 like-for-like payout currencies.\u003C\u002Fp>\n\u003Cp>Fraud Protection and 3D Secure\u003C\u002Fp>\n\u003Cp>The BlueSnap Payment Gateway offers Kount Fraud protection right from the plugin to best optimize the checkout flow. We also provide the option to select advanced fraud options if you want to customize your level of fraud screening.\u003Cbr \u002F>\nIn addition, as you sell to shoppers around the world, you will likely run into a location where you are required to support a 3D Secure checkout experience.  The BlueSnap Payment Gateway has built-in support for 3DS so you aren’t out of compliance in the regions where this is mandatory.\u003C\u002Fp>\n\u003Cp>Full support for Subscriptions and Pre-Orders\u003C\u002Fp>\n\u003Cp>The BlueSnap Payment Gateway provides support for \u003Cstrong>WooCommerce Subscriptions\u003C\u002Fstrong>, offering support for all of subscription features, including payment date changes, subscription date changes, and more. Note: The plugin doesn’t support multiple subscriptions in the same cart.\u003Cbr \u002F>\nThe gateway also fully supports \u003Cstrong>WooCommerce Pre-Orders\u003C\u002Fstrong>, so you can take customer’s payment information upfront and then automatically charge their payment method once the pre-order is released.\u003C\u002Fp>\n\u003Ch3>Recommended Versions\u003C\u002Fh3>\n\u003Cp>We recommend that you use the following versions when using the BlueSnap plugin for WooCommerce. The plugin may work when using older versions of PHP and MySQL as well; however, the following versions have been tested to ensure compatibility.\u003Cbr \u002F>\n* PHP: 8.2 or later\u003Cbr \u002F>\n* MySQL: 8.0 or later\u003Cbr \u002F>\n* WordPress: 6.6 or later\u003Cbr \u002F>\n* WooCommerce: 10.0 or later\u003Cbr \u002F>\n* WooCommerce Pre-Orders: 2.2 or later\u003Cbr \u002F>\n* WooCommerce Subscriptions: 7.5 or later\u003C\u002Fp>\n\u003Ch3>Software\u003C\u002Fh3>\n\u003Cp>This guide assumes that you have:\u003Cbr \u002F>\n* A working WordPress platform\u003Cbr \u002F>\nWooCommerce is a WordPress plugin that is installed on top of the WordPress platform. If you do not yet have a working WordPress installation, you may want to contact your website hosting provider, as many of them supply a quick-install process for WordPress.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>WooCommerce software installed and uploaded to your server.\u003Cbr \u002F>\nIf you need the plugin, go to: https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwoocommerce\u002F or to http:\u002F\u002Fwww.woothemes.com\u002Fwoocommerce\u002F to download the WooCommerce plugin.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you want to use the Pre-Orders or Subscription functionalities, make sure that the respective plugins are also installed in your WordPress website:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Pre-Orders:  http:\u002F\u002Fwww.woothemes.com\u002Fproducts\u002Fwoocommerce-pre-orders\u002F \u003C\u002Fli>\n\u003Cli>Subscriptions:  http:\u002F\u002Fwww.woothemes.com\u002Fproducts\u002Fwoocommerce-subscriptions\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>PCI compliance\u003C\u002Fh3>\n\u003Cp>A PCI compliance of SAQ-A is required.\u003C\u002Fp>\n\u003Cp>Setup Steps\u003C\u002Fp>\n\u003Ch3>Step 1: Configure your BlueSnap account settings\u003C\u002Fh3>\n\u003Cp>Before you install the BlueSnap extension, complete these steps in your BlueSnap account:\u003Cbr \u002F>\n1. Set up your BlueSnap API Credentials(https:\u002F\u002Fdevelopers.bluesnap.com\u002Fv8976-Basics\u002Fdocs\u002Fapi-credentials). Make note of your API user key and password; you need them in later steps.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Define the authorized IP address for your server.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Configure your payout settings (https:\u002F\u002Fsupport.bluesnap.com\u002Fdocs\u002Fpayout-method).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Step 2: Install the plugin\u003C\u002Fh3>\n\u003Cp>Install the BlueSnap Payment Gateway plugin, as follows:\u003Cbr \u002F>\n1. In WordPress, click \u003Cstrong>Plugins > Add New\u003C\u002Fstrong> in the left menu.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Search for \u003Ccode>BlueSnap\u003C\u002Fcode> in the search box in the top-right side.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Click the \u003Cstrong>BlueSnap Payment Gateway for WooCommerce\u003C\u002Fstrong> plugin and install it.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Click \u003Cstrong>Plugins > Installed Plugins\u003C\u002Fstrong> in the left menu.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>In the installed plugin screen, \u003Cstrong>activate\u003C\u002Fstrong> the following plugins, in this order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WooCommerce \u003C\u002Fli>\n\u003Cli>WooCommerce Subscriptions (optional) \u003C\u002Fli>\n\u003Cli>WooCommerce Pre-Orders (optional) \u003C\u002Fli>\n\u003Cli>BlueSnap Payment Gateway for WooCommerce \u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Important\u003C\u002Fstrong>\u003Cbr \u002F>\nIf these are not activated in the specified order, the installation will not complete properly.\u003C\u002Fp>\n\u003Ch3>Step 3: Set the Default Currency\u003C\u002Fh3>\n\u003Cp>Configure the default currency settings for WooCommerce by completing the following steps:\u003Cbr \u002F>\n1. Go to \u003Cstrong>WooCommerce > Settings > General\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Scroll down to \u003Cstrong>Currency Options\u003C\u002Fstrong> and set the values as necessary.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Click Save Changes.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Step 4: Configure the plugin\u003C\u002Fh3>\n\u003Cp>Configure the BlueSnap plugin using the following steps:\u003Cbr \u002F>\n1. Click the \u003Cstrong>Settings\u003C\u002Fstrong> link below the BlueSnap plugin. The BlueSnap page opens.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Configure the following settings. \u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Note\u003C\u002Fstrong>: You can find your BlueSnap information (API credentials, Merchant ID, and more) for the following settings in your BlueSnap Merchant Console in \u003Cstrong>Settings > API Settings\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable\u002FDisable\u003C\u002Fstrong> — Select Enable BlueSnap. This means that BlueSnap appears as a payment option during checkout. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test mode\u003C\u002Fstrong> — Select Enable Test Mode to use your BlueSnap Sandbox account, select the Enable Test Mode option. Leave the option cleared to use your BlueSnap Production account. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Title\u003C\u002Fstrong> — By default, this is Credit\u002FDebit Cards. This label is presented to the shopper when they choose a payment option during checkout. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Description\u003C\u002Fstrong> — By default, this is Pay using your Credit\u002FDebit Card. This describes the payment method during checkout. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>API User Key and API Password\u003C\u002Fstrong> — Enter your API User Key and Password for your BlueSnap account. Use your sandbox credentials if you chose Enable Test Mode above. Use your production credentials if you did not chose Enable Test Mode above. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Merchant ID\u003C\u002Fstrong> — Enter your Merchant ID number from your BlueSnap merchant account. \u003Cbr \u002F> \u003Cstrong>Note\u003C\u002Fstrong>: Use the Merchant ID from you sandbox or production environment, as applicable. They are different. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Soft Descriptor\u003C\u002Fstrong> — Enter a string, no more than 20 characters in length. This descriptor appears on the shopper’s billing statement to help them identify the purchase. You should use the same soft descriptor set in your BlueSnap Console. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Webhook (IPN) configuration\u003C\u002Fstrong> — Copy the URL from this section and use it for the Webhook Setup section below. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Header\u003C\u002Fstrong> — Enter the Security Header secret generated for the Endpoint in your BlueSnap Console -> Settings -> Webhook Settings. Webhook notifications will be rejected until this is configured. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Capture\u003C\u002Fstrong> — Whether or not to immediately capture the charge. When unchecked, the charge issues an authorization and will need to be captured later. This setting has no effect on subscriptions. Charges on orders related to subscriptions are always captured. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>3D Secure\u003C\u002Fstrong> — If you want to offer 3-D Secure, contact BlueSnap Merchant Support and ask for 3-D Secure to be enabled for your account. After that is done, you can select this option to activate 3-D Secure. For more information on 3-D Secure, refer to our 3-D Secure Guide (https:\u002F\u002Fsupport.bluesnap.com\u002Fdocs\u002F3d-secure).  \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Saved Cards\u003C\u002Fstrong> — Select this if you want to give logged-in shoppers the option to store their credit card details for future purchases. They can manage their information from their My Account area. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>BlueSnap currency converter\u003C\u002Fstrong> — BlueSnap works with many currencies (see a complete list at https:\u002F\u002Fsupport.bluesnap.com\u002Fdocs\u002Fcurrencies). The BlueSnap plugin for WooCommerce includes a built-in currency converter that you must configure in order to enable successful purchasing via BlueSnap. \u003Cbr \u002F>Select this option to use the converter. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Select the currencies to display in your shop\u003C\u002Fstrong> — Select all the currencies your WooCommerce store supports. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Google Pay Wallet\u003C\u002Fstrong> — If you want to offer Google Pay as a payment method for your shoppers, contact BlueSnap \u003Ca href=\"https:\u002F\u002Fbluesnap.zendesk.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew?ticket_form_id=360000127087\" rel=\"nofollow ugc\">Merchant Support\u003C\u002Fa> and ask for Google Pay to be enabled for your account. After that is done, you can select this option to allow shoppers to pay with Google Pay. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Google Merchant ID\u003C\u002Fstrong> — Enter your Google Business Merchant ID. Request for Google Pay production access [here]. Google Pay won’t be available in production mode until you enter the merchant ID. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Apple Pay Wallet\u003C\u002Fstrong> — If you want to offer Apple Pay as a payment method for your shoppers, contact BlueSnap \u003Ca href=\"https:\u002F\u002Fbluesnap.zendesk.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew?ticket_form_id=360000127087\" rel=\"nofollow ugc\">Merchant Support\u003C\u002Fa> and ask for Apple Pay to be enabled for your account. After that is done, you can select this option to allow shoppers to pay with Apple Pay. \u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logging\u003C\u002Fstrong> — Select the Log debug messages option to have communications between WooCommerce and BlueSnap recorded in the process log files. We recommend using this option during the development of your site or if you are experiencing any problems. \u003Cbr \u002F>To access process logs for the BlueSnap plugin, go to \u003Cstrong>WooCommerce > Status\u003C\u002Fstrong> and click the \u003Cstrong>Logs\u003C\u002Fstrong> tab. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Col>\n\u003Cli>Click Save Changes. \u003C\u002Fli>\n\u003Cli>If you would like to accept ACH payments, enable this feature by going to \u003Cstrong>WooCommerce > Settings > Payments\u003C\u002Fstrong> and setting the \u003Cstrong>BlueSnap ACH\u003C\u002Fstrong> toggle to \u003Cstrong>enable.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Click Save Changes.\u003Cbr \u002F>\n\u003Cstrong>Important\u003C\u002Fstrong>\u003Cbr \u002F>\nIf you plan to offer ACH as a payment method for subscriptions, please note:\u003Cbr \u002F>\nYou will need to contact Merchant Support to have this feature enabled.\u003Cbr \u002F>\nACH is not supported for subscriptions with daily billing, as banks take several days to authorize these charges.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Step 5: Secure checkout\u003C\u002Fh3>\n\u003Cp>Ensure that you are using secure checkout by completing the following steps.\u003Cbr \u002F>\n1. Go to \u003Cstrong>WordPress > Settings > General\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Col>\n\u003Cli>In the following URL fields, make sure that the URL begins with \u003Ccode>https:\u002F\u002F\u003C\u002Fcode>:\n\u003Cul>\n\u003Cli>\u003Cstrong>WordPress Address (URL)\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site Address (URL)\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Step 6. Webhook Setup\u003C\u002Fh3>\n\u003Cp>Webhooks (IPNs) trigger an HTTP POST message to your WooCommerce account when an important event occurs. Follow the steps below to set up Webhooks.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>Log in to your BlueSnap account and go to \u003Cstrong>Settings > Webhook Settings\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Update the \u003Cstrong>Endpoint URL(s)\u003C\u002Fstrong> field. The format of the URL should follow this pattern:\u003Cbr \u002F>\n  https:\u002F\u002Fwww.yourdomain.com\u002F?wc-api=bluesnap\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>In \u003Cstrong>Security Header\u003C\u002Fstrong>, toggle Add Security Header to the right to generate a unique encryption key that you can use to validate your webhook. Copy the value of the Security Header and paste it in the \u003Cstrong>Security Header\u003C\u002Fstrong> field in the plugin setting’s page.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>To enable specific Webhooks, toggle the button next to the Webhook to select it. We recommend enabling the following Webhook types:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AUTH_ONLY\u003C\u002Fli>\n\u003Cli>CANCEL_ON_RENEWAL\u003C\u002Fli>\n\u003Cli>CANCELLATION\u003C\u002Fli>\n\u003Cli>CANCELLATION_REFUND\u003C\u002Fli>\n\u003Cli>CHARGE\u003C\u002Fli>\n\u003Cli>CHARGEBACK\u003C\u002Fli>\n\u003Cli>CHARGEBACK_STATUS_CHANGED\u003C\u002Fli>\n\u003Cli>CONTRACT_CHANGE\u003C\u002Fli>\n\u003Cli>DECLINE\u003C\u002Fli>\n\u003Cli>FAILED_PAYOUT_TRANSFER\u003C\u002Fli>\n\u003Cli>RECURRING\u003C\u002Fli>\n\u003Cli>REFUND\u003C\u002Fli>\n\u003Cli>SUBSCRIPTION_REMINDER\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you plan to offer ACH as a payment method for subscriptions, make sure to select the \u003Cstrong>Subscription Charge Failure Webhook\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Click \u003Cstrong>Save\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>For more information on Webhooks, refer to our \u003Ca href=\"https:\u002F\u002Fsupport.bluesnap.com\u002Fdocs\u002Fabout-ipns\" rel=\"nofollow ugc\">Webhook documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Step 7: Crontab Setup\u003C\u002Fh3>\n\u003Cp>We recommend that you add a line to your crontab. The crontab is an application that runs in the server operating the WordPress application, and is in charge of periodic actions. It ensures that subscriptions continue to charge on time even if your WooCommerce store has no traffic, stores automatic renewals, and handles pre-orders.\u003Cbr \u002F>\nThe crontab file is available to you in most UNIX\u002FLinux based machines, and often can be found in \u003Ccode>\u002Fvar\u002Fspool\u002Fcron\u003C\u002Fcode>. If you are not sure where your crontab file is, reach out to your IT team or hosting provider for more details.\u003Cbr \u002F>\nYou should add the following line to your crontab file:\u003Cbr \u002F>\n    *\u002F15 * * * * {wget path} -q -O – {Web domain of your WooCommerce Store}\u002F wp-cron.php?doing_wp_cron\u003Cbr \u002F>\nFor example: \u003Ccode>*\u002F15 * * * * \u002Fusr\u002Fbin\u002Fwget -q -O - http:\u002F\u002Fshoppingcarts.bluesnap.com\u002Fwordpress\u002Fwp-cron.php?doing_wp_cron\u003C\u002Fcode>\u003Cbr \u002F>\nIf you have multiple WooCommerce Stores running on the same server, you should add this line for each one of them.\u003Cbr \u002F>\n\u003Cstrong>Note\u003C\u002Fstrong>:  \u003Ccode>*\u002F15\u003C\u002Fcode> makes the crontab run every 15 minutes. You can use this to change the cron frequency.\u003Cbr \u002F>\nFor additional help, contact BlueSnap Merchant Support (https:\u002F\u002Fbluesnap.zendesk.com\u002Fhc\u002Fen-us\u002Frequests\u002Fnew?ticket_form_id=360000127087).\u003Cbr \u002F>\n\u003Cstrong>Styling your payment form\u003C\u002Fstrong>\u003Cbr \u002F>\nBlueSnap supports the ability to customize the card elements (such as text color or font size) of the payment form. To do this, edit the BlueSnap plugin’s JavaScript by creating a bluesnapStyleOverrides object that contains your styling. See Supported selectors and Supported CSS properties for details https:\u002F\u002Fdevelopers.bluesnap.com\u002Fv8976-Tools\u002Fdocs\u002Fhosted-payment-fields#section-supported-css-properties. Use the code below as a starting point.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>const bluesnapStyleOverrides = {\n  '.invalid': {\n    \u002F\u002Fstyle all invalid elements\n    color: 'red'\n  },\n  '.valid': {\n    \u002F\u002Fstyle all valid elements\n    color: 'green'\n  },\n  ':focus': {\n    \u002F\u002Fstyle all elements on the focus event\n    color: 'orange'\n  },\n  '#ccn': {\n    \u002F\u002Fstyle only the card number element\n    color: 'blue'\n  },\n  '#cvv': {\n    \u002F\u002Fstyle only the CVV element\n    'font-size': '30px'\n  }\n};\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Customizing error messages\u003C\u002Fstrong>\u003Cbr \u002F>\nBlueSnap allows you to customize the messages of any errors that occur, giving you full control over the error descriptions that display in the UI or in error logs. To use this feature, you will need to add custom code to your WooCommerce account. We recommend using a plugin such as Code Snippets to accomplish this.\u003Cbr \u002F>\nUse the code sample below as a starting point. You can change error descriptions and add\u002Fremove errors from the code below.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter(\n  'wc_gateway_bluesnap_api_errors',\n  function ( $errors ) {\n      $errors = array(\n          '10000|INVALID_API_VERSION'        => __( 'API version is not correct...', 'woocommerce-bluesnap-gateway' ),\n          '10001|VALIDATION_GENERAL_FAILURE' => __( 'This is a val.gen. failure error.', 'woocommerce-bluesnap-gateway' ),\n          '14002'                            => __( 'This is the new error message for 14002', 'woocommerce-bluesnap-gateway' ),\n          '14002|SYSTEM_TECHNICAL_ERROR'     => __( 'This is the new error message for 14002|SYSTEM_TECHNICAL_ERROR', 'woocommerce-bluesnap-gateway' ),\n          '14016'                            => __( 'This is the new error message for 14016', 'woocommerce-bluesnap-gateway' ),\n      );\n      return $errors;\n  }\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Managing orders\u003C\u002Fstrong>\u003Cbr \u002F>\nIf card charges are not automatically captured, they will result in authorizations that need to be captured later. For example, if you sell physical goods, you will need to capture the authorization when the items are ready to be shipped out. Orders can be conveniently managed from your WooCommerce account by following these steps:\u003Cbr \u002F>\n1. Go to \u003Cstrong>WooCommerce > Orders\u003C\u002Fstrong> and click the order that you want to manage. The order’s status will be \u003Cstrong>On hold.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> ACH charges will also have a status of \u003Cstrong>On hold.\u003C\u002Fstrong> You don’t need to capture these charges.\u003Cbr \u002F>\n2. In the \u003Cstrong>Status\u003C\u002Fstrong> dropdown, select one of the following:\u003Cbr \u002F>\nIf you want to capture the authorization, select \u003Cstrong>Processing\u003C\u002Fstrong> or \u003Cstrong>Completed.\u003C\u002Fstrong>\u003Cbr \u002F>\nIf you want to cancel the authorization, select \u003Cstrong>Cancelled.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Tips for Checkout\u003C\u002Fstrong>\u003Cbr \u002F>\n– Don’t remove the Company Field since it’s a required field for ACH Corporate Accounts.\u003Cbr \u002F>\n– Consider adding the Store Notices block to your Checkout page if you are using the block Checkout and your theme is not a blocks based theme.\u003C\u002Fp>\n","Accept cards, ACH, Apple Pay and Google Pay, along with support for WooCommerce Subscriptions and Pre-orders on a global payments gateway.",9986,46,3,"2026-02-25T08:39:00.000Z","6.6","8.2",[77,78,79,80,81],"apple-pay","bluesnap","gateway","payment","woocommerce","https:\u002F\u002Fbluesnap.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbluesnap-payment-gateway-for-woocommerce.3.4.1.zip",97,"2026-02-13 16:19:36",{"slug":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":59,"downloaded":94,"rating":59,"num_ratings":60,"last_updated":95,"tested_up_to":96,"requires_at_least":97,"requires_php":51,"tags":98,"homepage":104,"download_link":105,"security_score":59,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"is-gallery","ImageSnippets Gallery Block","1.0.5","Henry Sautter (Hank)","https:\u002F\u002Fprofiles.wordpress.org\u002Fhlsautter\u002F","\u003Cp>This is a plugin for the Block Editor.\u003Cbr \u002F>\nIt creates a gallery block with images from \u003Ca href=\"https:\u002F\u002Fimagesnippets.com\" rel=\"nofollow ugc\">https:\u002F\u002Fimagesnippets.com\u003C\u002Fa>.\u003Cbr \u002F>\nImages will be evenly distributed in the space available.\u003Cbr \u002F>\nChanges to the set of images at imagesnippets are automatically shown in the gallery.\u003C\u002Fp>\n\u003Cp>Images tagged with “this image isin GALLERY” will be displayed.\u003Cbr \u002F>\n– GALLERY is the name of an image snippets entity.\u003C\u002Fp>\n\u003Cp>Optional Controls\u003Cbr \u002F>\n  – Display image captions.\u003Cbr \u002F>\n  – Display the gallery name as a title.\u003Cbr \u002F>\n  – Filter images by an imagesnippets userid.\u003Cbr \u002F>\n  – Sort the images by title or date.\u003Cbr \u002F>\n  – Limit the number of images displayed\u003Cbr \u002F>\n  – Styles change the thumbnail size.\u003C\u002Fp>\n\u003Ch3>Acknowledgments\u003C\u002Fh3>\n\u003Cp>d3-sparql \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fd3-sparql\u002Fv\u002F1.0.0\" rel=\"nofollow ugc\">https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fd3-sparql\u002Fv\u002F1.0.0\u003C\u002Fa>\u003Cbr \u002F>\nimagesnippets \u003Ca href=\"https:\u002F\u002Fimagesnippets.com\u002Flearn-more\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fimagesnippets.com\u002Flearn-more\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>What is Imagesnippetts?\u003C\u002Fh3>\n\u003Cp>ImageSnippets is an archival and curation tool. The goal of ImageSnippets is to build a persistent resource that establishes provenance and preserves the historical content and context of images. The application uses RDF syntax to ensure that the data entered will be readable in the future. RDF has become a standard, like HTML, and will likely be read by semantically aware devices for years to come. Additionally, the application saves data in a way that cannot be easily manipulated.\u003C\u002Fp>\n","Dynamic block to create an ImageSnippets gallery",6051,"2025-04-10T21:25:00.000Z","6.7.5","5.8",[99,100,101,102,103],"block","dynamic","gallery","imagesnippets","media","https:\u002F\u002Fimagesnippets.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fis-gallery.1.0.5.zip",{"slug":107,"name":108,"version":109,"author":110,"author_profile":111,"description":112,"short_description":113,"active_installs":11,"downloaded":114,"rating":13,"num_ratings":13,"last_updated":115,"tested_up_to":17,"requires_at_least":17,"requires_php":17,"tags":116,"homepage":122,"download_link":123,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"mesnevi-i-manevi","Mesnevi-i Manevi","1.1","sustun","https:\u002F\u002Fprofiles.wordpress.org\u002Fsustun\u002F","\u003Cp>Mevlânâ Celâleddin Rumî’nin altı ciltlik Farsça eseri, Mesnevî-i Manevî’den seçme beyitleri Türkçe olarak gösteren bir eklenti.\u003C\u002Fp>\n","Mevlânâ Celâleddin Rumî'nin altı ciltlik Farsça eseri, Mesnevî-i Manevî'den seçme beyitleri Türkçe olarak gösteren bir eklenti.",1584,"2010-08-27T01:45:00.000Z",[117,118,119,120,121],"celaleddin","manevi","mesnevi","mevlana","rumi","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fmesnevi-i-manevi\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmesnevi-i-manevi.zip",{"slug":125,"name":126,"version":127,"author":128,"author_profile":129,"description":130,"short_description":131,"active_installs":13,"downloaded":132,"rating":13,"num_ratings":13,"last_updated":133,"tested_up_to":134,"requires_at_least":135,"requires_php":136,"tags":137,"homepage":142,"download_link":143,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"yesnology","YesNology WordPress Plugin","1.0.0","Lorenzo Bonazzi","https:\u002F\u002Fprofiles.wordpress.org\u002Flbonazzi\u002F","\u003Cp>Through the plugin for YesNology it is possible to store the data entered by the user in a safe and reliable place 100% compliant with the GDPR. The plugin can be used for an unlimited number of collectors: collect newsletter subscriptions, customer satisfaction forms, customer surveys, … and much more!!!\u003C\u002Fp>\n\u003Cp>Through a short code you can collect all the information you deem appropriate. Through the YesNology backend you will be able to consult the data collected and you will be able to use them in a form compliant with the GDPR. You will also be able to share the collected data with your CRM using the APIs that YesNology makes available to you.\u003C\u002Fp>\n\u003Cp>To use the plugin you need to have a subscription to YesNology. You can find more information at https:\u002F\u002Fyesnology.com. You can contact us at info@yesnology.com\u003C\u002Fp>\n","YesNology Plugin for WordPress allows you to collect data from your website in a GDPR compliant way.",643,"2023-01-16T09:34:00.000Z","6.1.10","4.0.0","7.0.0",[138,139,140,141,125],"form","gdpr","newsletter","privacy","https:\u002F\u002Fyesnology.com\u002Fen\u002Fhow-does-it-work\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fyesnology.1.0.0.zip",{"attackSurface":145,"codeSignals":161,"taintFlows":179,"riskAssessment":215,"analyzedAt":224},{"hooks":146,"ajaxHandlers":157,"restRoutes":158,"shortcodes":159,"cronEvents":160,"entryPointCount":13,"unprotectedCount":13},[147,153],{"type":148,"name":149,"callback":150,"file":151,"line":152},"action","admin_menu","numly_add_option_page","numly.php",258,{"type":148,"name":154,"callback":155,"file":151,"line":156},"publish_post","numly_publish_post",259,[],[],[],[],{"dangerousFunctions":162,"sqlUsage":163,"outputEscaping":165,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":178},[],{"prepared":13,"raw":13,"locations":164},[],{"escaped":13,"rawEcho":166,"locations":167},5,[168,171,173,175,177],{"file":151,"line":169,"context":170},69,"raw output",{"file":151,"line":172,"context":170},121,{"file":151,"line":174,"context":170},128,{"file":151,"line":176,"context":170},143,{"file":151,"line":176,"context":170},[],[180,205],{"entryPoint":181,"graph":182,"unsanitizedCount":60,"severity":204},"numly_options_page (numly.php:92)",{"nodes":183,"edges":200},[184,189,193],{"id":185,"type":186,"label":187,"file":151,"line":188},"n0","source","$_POST['numly_settings']",99,{"id":190,"type":191,"label":192,"file":151,"line":188},"n1","transform","→ numly_post_options()",{"id":194,"type":195,"label":196,"file":197,"line":198,"wp_function":199},"n2","sink","update_option() [Settings Manipulation]","numly_functions.php",79,"update_option",[201,203],{"from":185,"to":190,"sanitized":202},false,{"from":190,"to":194,"sanitized":202},"low",{"entryPoint":206,"graph":207,"unsanitizedCount":60,"severity":204},"\u003Cnumly> (numly.php:0)",{"nodes":208,"edges":212},[209,210,211],{"id":185,"type":186,"label":187,"file":151,"line":188},{"id":190,"type":191,"label":192,"file":151,"line":188},{"id":194,"type":195,"label":196,"file":197,"line":198,"wp_function":199},[213,214],{"from":185,"to":190,"sanitized":202},{"from":190,"to":194,"sanitized":202},{"summary":216,"deductions":217},"The \"numly-numbers\" plugin version 2.6 exhibits a mixed security posture.  On the positive side, the static analysis shows no obvious direct attack vectors like unprotected AJAX handlers, REST API routes, or shortcodes.  Furthermore, all SQL queries are prepared, which is a strong security practice.  However, there are significant concerns regarding output escaping, with 0% of outputs being properly escaped. This suggests a high risk of Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected and executed in users' browsers. The taint analysis revealing two flows with unsanitized paths, though not classified as critical or high, is still a red flag and indicates potential for unexpected behavior or security issues if these paths involve user-supplied data.  The plugin's history of zero known vulnerabilities is a positive sign, suggesting past development efforts have been secure or issues have been promptly addressed.  However, this clean history should not overshadow the identified code-level risks, particularly the widespread lack of output escaping.",[218,221],{"reason":219,"points":220},"Output escaping is not implemented",15,{"reason":222,"points":223},"Taint flows with unsanitized paths",8,"2026-03-17T01:42:30.765Z",{"wat":226,"direct":239},{"assetPaths":227,"generatorPatterns":232,"scriptPaths":233,"versionParams":234},[228,229,230,231],"\u002Fwp-content\u002Fplugins\u002Fnumly-numbers\u002Fnumly.css","\u002Fwp-content\u002Fplugins\u002Fnumly-numbers\u002Fnumly_options.js","\u002Fwp-content\u002Fplugins\u002Fnumly-numbers\u002Fnumly.js","\u002Fwp-content\u002Fplugins\u002Fnumly-numbers\u002Fcss\u002Fstyle.css",[],[229,230],[235,236,237,238],"numly.css?ver=","numly_options.js?ver=","numly.js?ver=","style.css?ver=",{"cssClasses":240,"htmlComments":242,"htmlAttributes":247,"restEndpoints":252,"jsGlobals":253,"shortcodeOutput":254},[241],"numly-output",[243,244,245,246],"\u003C!--Creative Commons License-->","\u003C!--\u002FCreative Commons License-->","\u003C!-- Creative Commons Public Domain -->","\u003C!-- \u002FCreative Commons Public Domain -->",[248,249,250,251],"rel=\"license\"","alt=\"numly\"","alt=\"Creative Commons License\"","alt=\"Public Domain Dedication\"",[],[],[255,256,257,258,259,260],"\u003Cdiv class=\"numly-output\">","\u003Cimg align=\"bottom\" alt=\"numly\" src=\"http:\u002F\u002Fnumly.com\u002Fimages\u002Fnumly.png\" border=\"0\"\u002F>","\u003Ciframe height=\"50\" width=\"400\" src=\"http:\u002F\u002Fwww.numly.com\u002Fnumly\u002Fbarcode.asp?code=","&height=30\" name=\"munly1\" id=\"numly1\" scrolling=\"no\" frameborder=\"0\"\u002F>\u003C\u002Fiframe>","\u003Cimg alt=\"Creative Commons License\" border=\"0\" src=\"http:\u002F\u002Fcreativecommons.org\u002Fimages\u002Fpublic\u002Fsomerights20.png\"\u002F>","\u003Cimg alt=\"Public Domain Dedication\" border=\"0\" src=\"http:\u002F\u002Fi.creativecommons.org\u002Fl\u002Fpublicdomain\u002F88x31.png\" \u002F>"]