[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f_Lx0zdtvmUWpwW-8HgH4xbtLmcumVYb1icpJBhGSXSQ":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":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":37,"analysis":139,"fingerprints":206},"flywire-payment-gateway","Flywire for WooCommerce","1.0.11","taiflywire","https:\u002F\u002Fprofiles.wordpress.org\u002Ftaiflywire\u002F","\u003Cp>Flywire is a leading provider of cross-border as well as domestic payment solutions.  Our products are easy to integrate, offer competitive fess and are mostly free to use.  With this plugin, as well as an existing account with Flywire, any institution developing a WordPress + WooCommerce application can easily accept payments by Flywire, with minimal setup or configuration.\u003C\u002Fp>\n\u003Ch3>Disclaimer\u003C\u002Fh3>\n\u003Cp>By incorporating Flywire for WooCommerce scripts and related materials contained in the plugin file (collectively, the “Plugin”) onto your website, you acknowledge and agree to the following:\u003C\u002Fp>\n\u003Cp>The Plugin is only available for use by customers using Flywire’s services, which use is subject to Flywire’s onboarding process and your contractual agreement with Flywire.\u003C\u002Fp>\n\u003Cp>The Plugin is provided “as is.” Flywire Corporation (including its affiliates, employees, officers, directors, and shareholders) (collectively, “Flywire”) hereby disclaims all warranties of any kind, express or implied, by statute, at common law or otherwise, including, without limitation, the warranties of merchantability, fitness for a particular purpose and non-infringement. In no event shall Flywire be liable for any direct, indirect, special, incidental, or consequential damages or losses of any kind (including, but not limited to, loss of profits, the cost of procurement for substitute products or services, interruption of use, or loss or corruption of data), even if it is aware of the possibility of such damages. You understand that you download the Plugin at your own discretion and risk.\u003C\u002Fp>\n","Enable Flywire payments option for WooCommerce",90,5057,100,1,"2026-02-28T00:10:00.000Z","6.9.4","5.7","8.0",[20,21,22,23,24],"bank-transfer","credit-card","pay","payment-gateway","woocommerce","http:\u002F\u002Fwww.flywire.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fflywire-payment-gateway.1.0.11.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":33,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},2,93,30,89,"2026-04-04T06:07:28.852Z",[38,59,79,98,119],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":57,"download_link":58,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"woo-asaas","Asaas Gateway for WooCommerce","2.7.4","Asaas","https:\u002F\u002Fprofiles.wordpress.org\u002Fasaas\u002F","\u003Cp>Use \u003Ca href=\"https:\u002F\u002Fwww.asaas.com\" rel=\"nofollow ugc\">Asaas\u003C\u002Fa> as payment method in your WooCommerce store.\u003C\u002Fp>\n\u003Cp>This plugin is an implementation of \u003Ca href=\"https:\u002F\u002Fasaasv3.docs.apiary.io\" rel=\"nofollow ugc\">Asaas API v3\u003C\u002Fa>. The checkout mechanism is completely transparent. The customer will not go out of your store to finish the order. The data are sent to Asaas service, that process the payment and return its status.\u003C\u002Fp>\n\u003Cp>For any doubt about the plugin installation and integration, please read the FAQ. If it doesn’t solve, use the plugin Support area that we will help you as soon as possible.\u003C\u002Fp>\n","Take transparent credit card and bank ticket payment checkouts on your store using Asaas.",9000,177841,78,17,"2026-03-10T00:36:00.000Z","6.7.5","4.4","7.0",[55,21,56,23,24],"asaas","payment","https:\u002F\u002Fwww.asaas.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwoo-asaas.2.7.4.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":73,"tags":74,"homepage":77,"download_link":78,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"fr-multi-bank-transfer-payment-gateways-for-woocommerce","Fr Multi Bank Transfer Payment Gateways for WooCommerce","1.1.4","fahrirusliyadi","https:\u002F\u002Fprofiles.wordpress.org\u002Ffahrirusliyadi\u002F","\u003Cp>By default, WooCommerce provides 1 bank transfer payment gateway for all your bank accounts. With this plugin, you can add additional bank transfer payment gateways. So you can separate your bank accounts into multiple payment gateways, for example 1 payment gateway for 1 bank company.\u003C\u002Fp>\n\u003Cp>Notes:\u003Cbr \u002F>\n– On the screenshot you can see there are icons next to the payment gateway’s name. You can add the icon using \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffr-custom-payment-gateway-icon-for-woocommerce\u002F\" rel=\"ugc\">Fr Custom Payment Gateway Icon for WooCommerce\u003C\u002Fa> plugin.\u003C\u002Fp>\n","Add multiple bank transfer payment gateways.",2000,23213,14,"2025-09-13T03:03:00.000Z","6.8.5","4.9","",[75,20,76,23,24],"bacs","multiple","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffr-multi-bank-transfer-payment-gateways-for-woocommerce\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffr-multi-bank-transfer-payment-gateways-for-woocommerce.1.1.4.zip",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":87,"downloaded":88,"rating":11,"num_ratings":89,"last_updated":90,"tested_up_to":71,"requires_at_least":91,"requires_php":92,"tags":93,"homepage":96,"download_link":97,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"advance-bank-payment-transfer-gateway","Advance Bank Payment Transfer Gateway","1.0.0","Ramesh Kumar","https:\u002F\u002Fprofiles.wordpress.org\u002Fdeveloperramesh\u002F","\u003Cblockquote>\n\u003Cp>\u003Cstrong>Requires: WooCommerce 2.1+\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>This plugin clones the Direct Bank Transfer gateway to create another offline payment method. This can be used to create a testing payment method if you use the Advance Bank Transfer gateway.\u003Cbr \u002F>\nFor example, this could be used for manual invoices or other offline payment methods.\u003C\u002Fp>\n\u003Cp>Upload the Bank Payment Receipt is require on the checkout page before submit the page, When an order is submitted the order will be placed “on-hold” after reviewing order by admin then order status will be changed.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fcapsquery.com\u002F\" rel=\"nofollow ugc\"> Visit Our Website \u003C\u002Fa>\u003C\u002Fp>\n","Short Description: This plugin clones the Direct Bank Transfer gateway to create another offline payment method. License: GPLv2 or later",1000,24215,10,"2026-01-08T13:10:00.000Z","5.8","7.4",[20,94,95,23,24],"manual-payment","offline-payment","https:\u002F\u002Fgithub.com\u002Fdeveloper-ramesh","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadvance-bank-payment-transfer-gateway.1.0.0.zip",{"slug":99,"name":100,"version":101,"author":102,"author_profile":103,"description":104,"short_description":105,"active_installs":87,"downloaded":106,"rating":107,"num_ratings":108,"last_updated":109,"tested_up_to":16,"requires_at_least":110,"requires_php":53,"tags":111,"homepage":114,"download_link":115,"security_score":116,"vuln_count":117,"unpatched_count":27,"last_vuln_date":118,"fetched_at":29},"gestpay-for-woocommerce","Gestpay for WooCommerce","20251211","Fabrick Support","https:\u002F\u002Fprofiles.wordpress.org\u002Feasynolo\u002F","\u003Cp>Axerve Free Plugin for Woocommerce allows you to use \u003Ca href=\"https:\u002F\u002Fwww.axerve.com\u002F\" title=\"Axerve Website\" rel=\"nofollow ugc\">Axerve\u003C\u002Fa> on your WooCommerce-powered website.\u003C\u002Fp>\n\u003Cp>There are four operational modes in this plugin, which depends on Axerve version you are using:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Axerve Starter\u003C\u002Fli>\n\u003Cli>Axerve Professional\u003C\u002Fli>\n\u003Cli>Axerve Professional On Site\u003C\u002Fli>\n\u003Cli>Axerve Professional iFrame\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.axerve.com\u002Fit\u002Fplugin\u002Fwoocommerce\u002F\" title=\"Axerve for WooCommerce - Usage Documentation\" rel=\"nofollow ugc\">Click here to read the full usage documentation on Axerve\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>WooCommerce Blocks Compatibility\u003C\u002Fh4>\n\u003Cp>Starting from version 20251028, the plugin is fully compatible with WooCommerce Blocks checkout. All payment methods are now supported in both classic checkout and blocks checkout modes. There is no need to disable WooCommerce Blocks checkout.\u003C\u002Fp>\n\u003Ch4>Available Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>S2S SOAP (Except callReadTrxS2S and callVerifyCardS2S)\u003C\u002Fli>\n\u003Cli>Tokenization\u003C\u002Fli>\n\u003Cli>3DS1\u003C\u002Fli>\n\u003Cli>3DS2 – Authentication\u003C\u002Fli>\n\u003Cli>3DS2 – Recurring Transactions\u003C\u002Fli>\n\u003Cli>RBA (Risk-Based Authentication)\u003C\u002Fli>\n\u003Cli>PayPal Seller Protection\u003C\u002Fli>\n\u003Cli>WooCommerce Subscriptions support (Recurring payments and subscriptions)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Available Payment Methods\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Credit Cards\u003C\u002Fli>\n\u003Cli>BANCOMAT Pay\u003C\u002Fli>\n\u003Cli>MyBank\u003C\u002Fli>\n\u003Cli>PayPal\u003C\u002Fli>\n\u003Cli>PayPal Billing Agreement\u003C\u002Fli>\n\u003Cli>PayPal Buy Now Pay Later\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Actions and filters list\u003C\u002Fh3>\n\u003Cp>Here is a list of filters and actions used in this plugin:\u003C\u002Fp>\n\u003Ch4>Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>gestpay_before_processing_order\u003C\u002Fli>\n\u003Cli>gestpay_after_order_completed\u003C\u002Fli>\n\u003Cli>gestpay_after_order_failed\u003C\u002Fli>\n\u003Cli>gestpay_after_order_pending\u003C\u002Fli>\n\u003Cli>gestpay_before_order_settle\u003C\u002Fli>\n\u003Cli>gestpay_order_settle_success\u003C\u002Fli>\n\u003Cli>gestpay_order_settle_fail\u003C\u002Fli>\n\u003Cli>gestpay_before_order_refund\u003C\u002Fli>\n\u003Cli>gestpay_order_refund_success\u003C\u002Fli>\n\u003Cli>gestpay_order_refund_fail\u003C\u002Fli>\n\u003Cli>gestpay_before_order_delete\u003C\u002Fli>\n\u003Cli>gestpay_order_delete_success\u003C\u002Fli>\n\u003Cli>gestpay_order_delete_fail\u003C\u002Fli>\n\u003Cli>gestpay_after_s2s_order_failed\u003C\u002Fli>\n\u003Cli>gestpay_on_renewal_payment_failure\u003C\u002Fli>\n\u003Cli>gestpay_my_cards_template_before_table\u003C\u002Fli>\n\u003Cli>gestpay_my_cards_template_after_table\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filters\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>gestpay_gateway_parameters\u003C\u002Fli>\n\u003Cli>gestpay_encrypt_parameters\u003C\u002Fli>\n\u003Cli>gestpay_settings_tab\u003C\u002Fli>\n\u003Cli>gestpay_my_cards_template\u003C\u002Fli>\n\u003Cli>gestpay_cvv_fancybox\u003C\u002Fli>\n\u003Cli>gestpay_gateway_cards_images\u003C\u002Fli>\n\u003Cli>gestpay_alter_order_id -> this can be used to add, for example, a prefix to the order ID\u003C\u002Fli>\n\u003Cli>gestpay_revert_order_id -> this must be used to revert back the order ID changed with the \u003Ccode>gestpay_alter_order_id\u003C\u002Fcode> filter\u003C\u002Fli>\n\u003Cli>gestpay_s2s_validate_payment_fields\u003C\u002Fli>\n\u003Cli>gestpay_s2s_payment_fields_error_strings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Third Party Libraries\u003C\u002Fh3>\n\u003Cp>Questo plugin utilizza le seguenti librerie di terze parti:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>SOAP Client – Parte della libreria standard PHP, utilizzata per le comunicazioni con l’API Gestpay\u003C\u002Fli>\n\u003Cli>WooCommerce – Framework e-commerce per WordPress (GPLv3)\u003C\u002Fli>\n\u003Cli>WordPress – CMS principale (GPLv2 o successiva)\u003C\u002Fli>\n\u003Cli>jQuery – Libreria JavaScript per la manipolazione del DOM e la gestione degli eventi (MIT License)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>Questo plugin si connette ai seguenti servizi esterni:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Axerve Payment Gateway (precedentemente Gestpay)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>– Scopo: Elaborazione dei pagamenti tramite il gateway di Banca Sella\u003Cbr \u002F>\n– Dati inviati: Informazioni sull’ordine, dati del cliente necessari per il pagamento\u003Cbr \u002F>\n– Quando: Durante il processo di pagamento e per le operazioni di gestione degli ordini\u003Cbr \u002F>\n– Privacy Policy: https:\u002F\u002Fwww.axerve.com\u002Fprivacy-policy\u003Cbr \u002F>\n– Termini di servizio: https:\u002F\u002Fwww.axerve.com\u002Fterms-conditions\u003C\u002Fp>\n\u003Col>\n\u003Cli>icanhazip.com\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>– Scopo: Identificazione dell’indirizzo IP del server per la configurazione del gateway di pagamento\u003Cbr \u002F>\n– Dati inviati: Nessun dato viene inviato, il servizio risponde solo con l’indirizzo IP pubblico\u003Cbr \u002F>\n– Quando: Solo nell’area amministrativa durante la configurazione del plugin\u003Cbr \u002F>\n– Privacy Policy: https:\u002F\u002Fmajor.io\u002Ficanhazip-com-faq\u002F\u003Cbr \u002F>\n– Note: Questo servizio viene utilizzato solo per aiutare gli amministratori a configurare correttamente il gateway di pagamento nel backoffice di Axerve\u003C\u002Fp>\n\u003Col>\n\u003Cli>Script JavaScript di verifica\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>– Scopo: Verifica della compatibilità del browser con il gateway di pagamento\u003Cbr \u002F>\n– Dati inviati: Informazioni sul browser dell’utente per verificare la compatibilità TLS\u003Cbr \u002F>\n– Quando: Durante il processo di pagamento\u003Cbr \u002F>\n– Domini: gestpay.net, gestpay.it, ecomm.sella.it\u003Cbr \u002F>\n– Privacy Policy: https:\u002F\u002Fwww.axerve.com\u002Fprivacy-policy\u003C\u002Fp>\n\u003Col>\n\u003Cli>MyBank\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>– Scopo: Integrazione con il sistema di pagamento MyBank\u003Cbr \u002F>\n– Dati inviati: Informazioni necessarie per il pagamento tramite MyBank\u003Cbr \u002F>\n– Quando: Solo quando l’utente sceglie MyBank come metodo di pagamento\u003Cbr \u002F>\n– Privacy Policy: https:\u002F\u002Fwww.mybank.eu\u002Fprivacy-policy\u002F\u003Cbr \u002F>\n– Termini di servizio: https:\u002F\u002Fwww.mybank.eu\u002Fterms-and-conditions\u002F\u003C\u002Fp>\n\u003Cp>Server di test e sviluppo\u003Cbr \u002F>\nNel codice di esempio (directory \u003Ccode>sample\u002F\u003C\u002Fcode>) sono presenti riferimenti a domini fittizi (\u003Ccode>site1.it\u003C\u002Fcode> e \u003Ccode>site2.it\u003C\u002Fcode>) utilizzati solo come esempio per dimostrare la configurazione multi-sito. Questi domini sono puramente dimostrativi e non sono utilizzati nel codice di produzione.\u003C\u002Fp>\n","Axerve Free Plugin for Woocommerce extends WooCommerce providing the payment gateway Axerve.",43366,76,9,"2025-12-11T15:15:00.000Z","4.7",[112,21,113,23,24],"axerve","gestpay","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fgestpay-for-woocommerce\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgestpay-for-woocommerce.20251211.zip",99,3,"2024-02-27 00:00:00",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":87,"downloaded":127,"rating":27,"num_ratings":27,"last_updated":128,"tested_up_to":16,"requires_at_least":129,"requires_php":92,"tags":130,"homepage":136,"download_link":137,"security_score":33,"vuln_count":117,"unpatched_count":27,"last_vuln_date":138,"fetched_at":29},"payplus-payment-gateway","PayPlus Payment Gateway","8.1.5","PayPlus Tech Team","https:\u002F\u002Fprofiles.wordpress.org\u002Fpayplus\u002F","\u003Cp>PayPlus Payment Gateway for WooCommerce\u003Cbr \u002F>\nAccept debit and credit cards on your WooCommerce store in a secure way with the ability to design your own payment page and add high functionalities to it. SSL is not required.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Supported PHP Versions:\u003C\u002Fstrong>\u003Cbr \u002F>\nThis plugin is compatible with PHP versions from 7.4 up to 8.3.\u003C\u002Fp>\n\u003Cp>Before installation:\u003Cbr \u002F>\nYou need your account credentials. For that, you have to contact PayPlus and to join the service.\u003C\u002Fp>\n\u003Cp>Plugin Disclaimer:\u003Cbr \u002F>\nPayPlus does not accept liability for any damage, loss, cost (including legal costs), expenses, indirect losses or consequential damage of any kind which may be suffered or incurred by the user from the use of this service.\u003C\u002Fp>\n\u003Cp>It is important to know that this plugin relies on third-party services.\u003Cbr \u002F>\nHowever, the third-party so mentioned is the PayPlus core engine at their servers – the providers of this plugin.\u003C\u002Fp>\n\u003Cp>By being a payment processor, just like many of its kind, it must send some transaction details to the third-party server (itself) for token generation and transaction logging statistics and connecting to invoices.\u003C\u002Fp>\n\u003Cp>It is this transfer back and forth of data between your WooCommerce and the PayPlus servers that we would like to bring to your attention clearly and plainly.\u003C\u002Fp>\n\u003Cp>The main links to PayPlus, its terms and conditions, and privacy policy are as listed:\u003Cbr \u002F>\n– Home Page: https:\u002F\u002Fwww.payplus.co.il\u003Cbr \u002F>\n– Plugin Instruction page: https:\u002F\u002Fwww.payplus.co.il\u002Fwordpress\u003Cbr \u002F>\n– Terms and Conditions: https:\u002F\u002Fwww.payplus.co.il\u002Fprivacy\u003C\u002Fp>\n\u003Cp>The above records, the transaction details, are not treated as belonging to PayPlus and are never used for any other purposes.\u003C\u002Fp>\n\u003Cp>The external files referenced by this plugin, due to WordPress policy recommendations, are all included in the plugin directory.\u003C\u002Fp>\n\u003Ch3>8.1.5  – 15-03-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Feature   – Added VAT selection prompt for partial refunds, allowing admins to choose whether the refunded amount includes VAT or is VAT-exempt.\u003C\u002Fli>\n\u003Cli>Fix       – Resolved an issue where saved payment tokens could override the PayPlus Embedded selection, causing the checkout to revert to a previously saved card instead of using newly entered card details.\u003C\u002Fli>\n\u003Cli>Fix       – Fixed token saving failure when the optional “Name for Invoice” or “Alternative ID\u002FVAT” fields were filled during PayPlus Embedded checkout.\u003C\u002Fli>\n\u003Cli>Feature   – PRUID history tracking: all payment page request UIDs are now stored with timestamps, enabling recovery of orders where the UID changed. The “Get PayPlus Data” button shows a selection popup with a “Try All” option.\u003C\u002Fli>\n\u003Cli>Feature   – Optional order total display inside PayPlus Embedded payment form for both Classic and Blocks checkout, with automatic updates on coupon\u002Fshipping changes.\u003C\u002Fli>\n\u003Cli>Tweak     – Reduced checkout order-status polling frequency to prevent excessive server load on slower sites.\u003C\u002Fli>\n\u003Cli>Fix       – Fixed Hebrew character corruption (appearing as raw Unicode escapes) in PayPlus API payloads for certain server configurations.\u003C\u002Fli>\n\u003Cli>Tweak     – PRUID history is now used by the cron job and the Orders Validator for more reliable order status recovery.\u003C\u002Fli>\n\u003Cli>Fix       – Fixed expiry field order in PayPlus Embedded for LTR locales.\u003C\u002Fli>\n\u003Cli>Fix       – The “Include Apple Pay Script” setting now correctly loads the Apple Pay script on Blocks checkout for all iframe display modes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.4  – 10-03-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Fixed an issue where redirect URLs after payment could be malformed (& converted to &), potentially causing broken thank-you page loads or missing order details.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.3  – 25-02-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Resolved “Redirect” and “Next page iframe” display issues on the order-pay page for specific customer environments caused by an unnecessary static flag preventing proper rendering.\u003C\u002Fli>\n\u003Cli>Feature   – Added inline loader to PayPlus Embedded “Place Order” button, providing immediate visual feedback during payment processing for improved user experience. \u003C\u002Fli>\n\u003Cli>Tweak     – Addressed WordPress Plugin Check (PCP) compliance requirements.\u003C\u002Fli>\n\u003Cli>Fix       – Improved Invoice+ error message handling on the orders page to properly display API error details.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.2  – 24-02-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Feature   – Full PW Gift Cards integration for Blocks Checkout across all PayPlus payment methods, including correct discount handling, order totals, and debit timing.\u003C\u002Fli>\n\u003Cli>Fix       – PW Gift Cards discount now applied correctly in Iframe (next page) and Redirect modes in Blocks Checkout, consistent with Popup and Same-Page Iframe behavior.\u003C\u002Fli>\n\u003Cli>Feature   – Added option to mark the Customer Invoice Name field as required in both Classic and Blocks Checkout.\u003C\u002Fli>\n\u003Cli>Feature   – Added option to set a custom label and placeholder for the Customer Invoice Name field in both Classic and Blocks Checkout.\u003C\u002Fli>\n\u003Cli>Tweak     – PayPlus Embedded loader: when “Hide PayPlus logo when showing loader” is enabled, “Processing Payment…” (or its Hebrew translation) is now always centered in the loader and displayed clearly.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.1  – 23-02-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – TV power-down effect in Blocks Checkout is now driven by the plugin setting rather than CSS positioning, ensuring it triggers reliably regardless of theme styles.\u003C\u002Fli>\n\u003Cli>Tweak     – Blocks Checkout popup and same-page iframe modes now open instantly — the PayPlus payment page link is fetched asynchronously after checkout submission instead of blocking the Store API response.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.0  – 22-02-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Improved redirect handling across all browsers with a unified solution, eliminating the need for browser-specific settings and checkboxes.\u003C\u002Fli>\n\u003Cli>Tweak     – Added translated “Payment received – redirecting…” screen that appears briefly when using fallback redirect method.\u003C\u002Fli>\n\u003Cli>Fix       – Resolved issue where changing delivery method in classic checkout would incorrectly switch the selected payment method in the payment list.\u003C\u002Fli>\n\u003Cli>Tweak     – Callback handler now processes orders in “failed” status (in addition to “pending”) since callbacks occur after order creation and payment.\u003C\u002Fli>\n\u003Cli>Added     – Optional TV power-down effect for popup iframe mode. When enabled via plugin settings, displays a classic CRT television shutdown animation before redirecting to thank you page.\u003C\u002Fli>\n\u003Cli>Fix       – Order payment method now reflects the actual payment method used (e.g., credit card, Google Pay, Bit) rather than the initially selected gateway, ensuring accuracy in WooCommerce order details and invoices.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.0.9  – 18-02-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Fixed default setting for Firefox-compatible redirect mode – polling fallback is now enabled by default as intended.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.0.7  – 18-02-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Tweak     – Added automatic polling fallback for iframe payment redirects in both blocks and classic checkouts. This ensures reliable redirects for Firefox users and other scenarios where the iframe cannot communicate via postMessage. The system polls the server for order completion status and redirects to the thank-you page automatically.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Fix       – Fixed EMV POS device functionality issue when only one admin user was configured.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Tweak – Improved the \u003Ccode>payPlusRemote()\u003C\u002Fcode> function to better handle \u003Ccode>$payload\u003C\u002Fcode> issues.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>Tweak – Removed outdated logs and deprecated API calls.\u003C\u002Fli>\n\u003Cli>Tweak – Optimized payment page logic to reuse existing pages when possible, reducing unnecessary API requests.\u003C\u002Fli>\n\u003Cli>Tweak – Corrected inaccurate status reporting in “Orders Reports\u002FValidator”.\u003C\u002Fli>\n\u003Cli>Tweak – Streamlined \u003Ccode>callback_response\u003C\u002Fcode> by removing redundant functions and passing data directly instead of using SQL.\u003C\u002Fli>\n\u003Cli>Added – When “Update status in IPN” is enabled, the callback function will skip status updates and related checks.\u003C\u002Fli>\n\u003Cli>Added – Disallow voucher payment for shipping – Enforce a minimum amount for non-voucher payments: voucher payments can no longer be used to pay for shipping, preventing customers from covering delivery costs with vouchers.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fpayplus-payment-gateway\u002Ftrunk\u002FCHANGELOG.md\" rel=\"nofollow ugc\">See changelog for all versions\u003C\u002Fa>.\u003C\u002Fp>\n","Accept credit\u002Fdebit card payments or other methods such as bit, Apple Pay, Google Pay in one page. Create digitally signed invoices & much more!",79632,"2026-03-15T06:09:00.000Z","6.2",[131,132,133,134,135],"charges-and-refunds","credit-cards","subscriptions","tokenization","woocommerce-payment-gateway","https:\u002F\u002Fwww.payplus.co.il\u002Fwordpress","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpayplus-payment-gateway.8.1.5.zip","2024-07-09 00:00:00",{"attackSurface":140,"codeSignals":182,"taintFlows":193,"riskAssessment":194,"analyzedAt":205},{"hooks":141,"ajaxHandlers":174,"restRoutes":175,"shortcodes":176,"cronEvents":181,"entryPointCount":14,"unprotectedCount":27},[142,148,154,158,162,166,170],{"type":143,"name":144,"callback":145,"file":146,"line":147},"filter","woocommerce_payment_gateways","flywire_pay_add_to_gateways","flywire-payment-gateway.php",48,{"type":149,"name":150,"callback":151,"priority":152,"file":146,"line":153},"action","plugins_loaded","flywire_pay_gateway_init",11,134,{"type":149,"name":155,"callback":156,"priority":89,"file":146,"line":157},"woocommerce_email_before_order_table","email_instructions",347,{"type":149,"name":159,"callback":160,"file":146,"line":161},"wp_enqueue_scripts","add_plugin_scripts",348,{"type":149,"name":163,"callback":164,"file":146,"line":165},"woocommerce_after_checkout_form","checkout_button",349,{"type":143,"name":167,"callback":168,"priority":89,"file":146,"line":169},"woocommerce_thankyou_order_received_text","flywire_thankyou_order_received_text",350,{"type":149,"name":171,"callback":172,"file":173,"line":34},"woocommerce_api_wc_gateway_flywire","check_response","includes\\flywire-payment-gateway-callback-handler.php",[],[],[177],{"tag":178,"callback":179,"file":146,"line":180},"flywire_order_pay","flywire_shortcode_pay",117,[],{"dangerousFunctions":183,"sqlUsage":184,"outputEscaping":186,"fileOperations":14,"externalRequests":32,"nonceChecks":27,"capabilityChecks":27,"bundledLibraries":192},[],{"prepared":27,"raw":27,"locations":185},[],{"escaped":187,"rawEcho":14,"locations":188},4,[189],{"file":146,"line":190,"context":191},836,"raw output",[],[],{"summary":195,"deductions":196},"The \"flywire-payment-gateway\" plugin v1.0.11 demonstrates a generally good security posture based on the provided static analysis. The absence of direct SQL injection vulnerabilities due to the exclusive use of prepared statements and the handling of external HTTP requests are positive indicators. Furthermore, the limited attack surface, with no unprotected AJAX handlers or REST API routes, contributes to a relatively secure foundation. The plugin also appears to have a clean vulnerability history, with no known CVEs, which is a significant strength.\n\nHowever, there are a few areas that warrant attention. The presence of file operations, even if only one, without explicit details on its nature, could potentially introduce risks if not handled securely. Similarly, the lack of nonce checks on the single shortcode is a concern, as shortcodes can be exploited if they handle user input without proper verification. The 80% proper output escaping, while good, means that 20% of outputs are not properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities.\n\nIn conclusion, the plugin has strong foundational security practices, particularly concerning database interactions and its limited attack surface. The primary risks lie in the potential for XSS due to unescaped output and the absence of nonce checks on its shortcode. The clean vulnerability history is reassuring, but the identified code signals suggest areas where security could be further hardened.",[197,200,203],{"reason":198,"points":199},"Unescaped output (20% of total)",6,{"reason":201,"points":202},"Missing nonce checks on shortcode",5,{"reason":204,"points":117},"File operations without explicit context","2026-03-16T21:19:50.588Z",{"wat":207,"direct":216},{"assetPaths":208,"generatorPatterns":211,"scriptPaths":212,"versionParams":213},[209,210],"\u002Fwp-content\u002Fplugins\u002Fflywire-payment-gateway\u002Fcss\u002Fflywire.css","\u002Fwp-content\u002Fplugins\u002Fflywire-payment-gateway\u002Fjs\u002Fflywire.js",[],[210],[214,215],"flywire-payment-gateway\u002Fcss\u002Fflywire.css?ver=","flywire-payment-gateway\u002Fjs\u002Fflywire.js?ver=",{"cssClasses":217,"htmlComments":219,"htmlAttributes":226,"restEndpoints":248,"jsGlobals":249,"shortcodeOutput":251},[218],"flywire-payment-form",[5,220,221,222,223,224,225],"Provides a Flywire Payment Gateway","Plugin installing:","Created page \"\u002Fpay-with-flywire\": ","Plugin uninstalling:","Removed page \"\u002Fpay-with-flywire\": ","Removed shortcode \"flywire_order_pay\".",[227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247],"data-flywire-portal","data-flywire-order-id","data-flywire-locale","data-flywire-return-url","data-flywire-amount","data-flywire-currency","data-flywire-payer-email","data-flywire-payer-first-name","data-flywire-payer-last-name","data-flywire-payer-phone","data-flywire-payer-address-line1","data-flywire-payer-address-line2","data-flywire-payer-address-city","data-flywire-payer-address-state","data-flywire-payer-address-zip","data-flywire-payer-address-country","data-flywire-display-payer-info","data-flywire-hidden-payer-fields","data-flywire-enable-header","data-flywire-enable-footer","data-flywire-enable-chat",[],[250],"flywire_payment",[252],"[flywire_order_pay]"]