[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fyYDfdyzOcLNTnm5F3K70D6ow8zqdRv9S7i7EqZnR9ww":3,"$fazdxnfSzyu1677zhceN_lYzbVaPf0j4JAGgqx4ke5mY":238,"$fg1LEgnGV-yb9Btita93s4yHq4x0iH_4MONCTpxKmRKk":243},{"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,"discovery_status":30,"vulnerabilities":31,"developer":32,"crawl_stats":28,"alternatives":38,"analysis":141,"fingerprints":215},"recurring-payment-woo-ccbill","Payment Gateway for CCBill One Time and Recurring – Woo and WooSubscription","1.1.0","NephilaINC (Sunil and Jay)","https:\u002F\u002Fprofiles.wordpress.org\u002Fswetark\u002F","\u003Cp>\u003Cstrong>Accept CCBill One-Time & Recurring Payments in WooCommerce.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin integrates CCBill with your WooCommerce store, allowing you to accept both one-time and recurring payments via CCBill FlexForms. It also supports WooCommerce Subscriptions for recurring billing workflows.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Accept one-time and recurring CCBill payments\u003C\u002Fli>\n\u003Cli>Compatible with WooCommerce Subscriptions\u003C\u002Fli>\n\u003Cli>Supports CCBill FlexForms\u003C\u002Fli>\n\u003Cli>Supports WooCommerce Checkout Blocks\u003C\u002Fli>\n\u003Cli>Declares WooCommerce HPOS compatibility\u003C\u002Fli>\n\u003Cli>Prevents multiple subscriptions in the same cart\u003C\u002Fli>\n\u003Cli>Supports multiple CCBill currency codes: USD, EUR, GBP, CAD, AUD, JPY\u003C\u002Fli>\n\u003Cli>Subscription cancellation support through CCBill DataLink API\u003C\u002Fli>\n\u003Cli>Built-in setup instructions and webhook URL display\u003C\u002Fli>\n\u003Cli>Debug logging with sensitive values redacted\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>Note: Recurring payments require the WooCommerce Subscriptions plugin.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin integrates with CCBill for payment processing.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Services Used:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>https:\u002F\u002Fapi.ccbill.com — used for FlexForm payment redirection\u003C\u002Fli>\n\u003Cli>https:\u002F\u002Fdatalink.ccbill.com — used for subscription cancellation requests when DataLink credentials are configured\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Data Sent:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>During checkout, customer billing details, order amount, CCBill account\u002Fsub-account values, FlexForm ID, currency code, and WooCommerce order ID are sent to CCBill so CCBill can process the payment. For recurring products, subscription pricing\u002Fperiod data is also sent.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service Policies:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Terms of Use: https:\u002F\u002Fwww.ccbill.com\u002Fterms-of-use\u003C\u002Fli>\n\u003Cli>Privacy Policy: https:\u002F\u002Fwww.ccbill.com\u002Fprivacy-notice\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>Need help setting up?\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Email: info@nephilainc.com\u003C\u002Fli>\n\u003Cli>WhatsApp: +91 9913783777\u003C\u002Fli>\n\u003Cli>Skype: joomlaexpert.ce@gmail.com\u003C\u002Fli>\n\u003Cli>Website: https:\u002F\u002Fnephilainc.com\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Donate\u003C\u002Fh3>\n\u003Cp>If this plugin helps your business, consider buying me a coffee: https:\u002F\u002Fnephilainc.com\u002F\u003C\u002Fp>\n","Accept both one-time and recurring WooCommerce payments via CCBill with FlexForms and WooCommerce Subscriptions support.",10,719,100,4,"2026-06-11T05:05:00.000Z","6.8.6","5.0","7.0",[20,21,22,23,24],"credit-card","payment-gateway","recurring-payments","subscription","woocommerce","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frecurring-payment-woo-ccbill.1.1.0.zip",0,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":11,"avg_security_score":13,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"swetark",2,30,94,"2026-08-29T08:11:34.275Z",[39,64,82,102,119],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":27,"num_ratings":27,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":59,"download_link":60,"security_score":61,"vuln_count":62,"unpatched_count":27,"last_vuln_date":63,"fetched_at":29},"payplus-payment-gateway","PayPlus Payment Gateway","8.2.3","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.2.3  – 08-07-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Feature   – New “Show loader during iframe payment & redirect” option: displays a processing spinner over the iframe when payment is submitted, then a full-screen redirect loader when order completes.\u003C\u002Fli>\n\u003Cli>Fix       – Classic checkout: reopening an iframe popup\u002Fsame-page payment after closing without paying no longer falls back to redirect mode (duplicate payment page fix now correctly returns the cached link for inline modes).\u003C\u002Fli>\n\u003Cli>Fix       – Blocks checkout: processing loader, if activated, no longer appears immediately when the iframe opens; it now correctly waits for the user’s payment submission.\u003C\u002Fli>\n\u003Cli>Fix       – Cron: payment_complete() now fires while the order is still pending (matching regular callback behavior), ensuring the “Payment complete” order note is recorded.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.2.2  – 24-06-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Security  – Hosted payment and order completion AJAX handlers now verify order ownership before acting. Prevents unauthenticated metadata tampering and order-key disclosure. (Reported by Pedro Pinho and kevin @OPCIA via WPScan\u002FAutomattic)\u003C\u002Fli>\n\u003Cli>Fix       – Checkout: “Place Order” button no longer flickers when switching payment methods.\u003C\u002Fli>\n\u003Cli>Fix       – Cron: when “Payment Completed” is enabled, cron-recovered orders now correctly fire the woocommerce_payment_complete hook.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.2.1  – 10-06-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Payment page: prevented duplicate payment page creation per order by saving the meta fields the existing duplicate-prevention guard relies on. Eliminates duplicate PRUID entries.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.2.0  – 07-06-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Cron: when “Exclude manually cancelled orders from cron” checkbox is enabled, orders cancelled by an admin or shop manager are now excluded from cron instead of deleting payment data.\u003C\u002Fli>\n\u003Cli>Fix       – Cron: order status change hook registers only once, preventing duplicate order notes. Works for admins and shop managers via admin, AJAX, or REST.\u003C\u002Fli>\n\u003Cli>Fix       – Cron: minimum order age reduced to 10 minutes for faster processing.\u003C\u002Fli>\n\u003Cli>Tweak     – Settings: cancel checkbox relabeled to “Exclude manually cancelled orders from cron”.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.9  – 03-06-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Blocks checkout: validation errors no longer show a persistent PayPlus error popup; WooCommerce native inline notices are used instead.\u003C\u002Fli>\n\u003Cli>Fix       – Blocks checkout: corrected set_payment_details calls to pass arrays instead of strings, preventing PHP foreach warnings.\u003C\u002Fli>\n\u003Cli>Fix       – Hosted Fields: card number field now shows a green checkmark when card brand is detected.\u003C\u002Fli>\n\u003Cli>Fix       – Hosted Fields: lock and CVV icons now use inline data URIs, eliminating CORS errors on local\u002Fdev environments.\u003C\u002Fli>\n\u003Cli>Fix       – SEO: noindex meta tag for error page no longer incorrectly applied to other pages.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.8  – 19-05-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Feature   – Invoice+ Documents: Added POS EMV to the “Do not create documents” exclusion list.\u003C\u002Fli>\n\u003Cli>Fix       – Invoice+ Documents: POS EMV exclusion now works correctly (POS EMV orders are detected via transaction meta).\u003C\u002Fli>\n\u003Cli>Fix       – Invoice+ Documents: Payment method detection now uses alternative_method_name (bit, apple-pay, google-pay) when available.\u003C\u002Fli>\n\u003Cli>Fix       – Invoice+ Documents: Payment query is now HPOS-compatible (queries correct meta table on High-Performance Order Storage sites) – Fix for docs that came out as other instead of payment app.\u003C\u002Fli>\n\u003Cli>Fix       – Payment meta is now fully stored before order save, preventing race conditions with automatic invoice creation hooks.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.7  – 05-05-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – Resolved WC_Order_Item_Coupon::offsetGet deprecation notice (since WooCommerce 4.4.0) when coupons are applied at checkout.\u003C\u002Fli>\n\u003Cli>Feature   – Refund fee: Option to automatic 5% or 100 NIS (whichever is lower) refund fee for PayPlus refunds.\u003C\u002Fli>\n\u003Cli>Feature   – POS Only Mode option for dedicated POS terminal setups.\u003C\u002Fli>\n\u003Cli>Fix       – Hide PayPlus Gateway checkbox now works reliably for all checkout types (Classic and Blocks), regardless of Hosted Fields or EMV configuration.\u003C\u002Fli>\n\u003Cli>Fix       – Hosted Fields: resolved duplicate rendering issues on Blocks checkout.\u003C\u002Fli>\n\u003Cli>Fix       – Subscriptions: token now correctly retrieved from subscription or parent order (ON ALL CASES).\u003C\u002Fli>\n\u003Cli>Fix       – Blocks checkout: payment errors now display correctly to frontend users.\u003C\u002Fli>\n\u003Cli>Fix       – Cron job no longer fires at order creation, only at scheduled intervals.\u003C\u002Fli>\n\u003Cli>Tweak     – Optimized user_has_cap filter: now registers only once and only in admin, eliminating ~200ms overhead on every frontend request.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>8.1.6  – 18-03-2026\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Fix       – PayPlus payment gateway now displays correctly in the WooCommerce Blocks checkout page editor (resolved “payment methods not supported” message).\u003C\u002Fli>\n\u003Cli>Feature   – Blocks checkout: closing a payment page (iframe\u002Fpopup) or re-selecting a payment method no longer requires a full page reload.\u003C\u002Fli>\n\u003Cli>Fix       – Blocks checkout: PayPlus Embedded (hosted fields) no longer requires a full page reload on payment failure or when coupons\u002Fgift cards change.\u003C\u002Fli>\n\u003Cli>Fix       – Order status polling now stops correctly when a payment page is closed or the cart total changes (both Classic and Blocks checkout).\u003C\u002Fli>\n\u003Cli>Feature   – J5 Weight Estimate: added a configurable percentage-based cart fee (5%–20%) for Authorization (J5) mode, visible only when a PayPlus gateway is selected.\u003C\u002Fli>\n\u003Cli>Feature   – J5 Weight Estimate: customizable fee name and optional description message displayed below the fee line.\u003C\u002Fli>\n\u003Cli>Feature   – New option to prevent double rendering of the payment page iframe on the receipt page (common with Elementor or other page builders).\u003C\u002Fli>\n\u003Cli>Tweak     – Removed TV power-down effect feature.\u003C\u002Fli>\n\u003C\u002Ful>\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\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!",1000,87015,"2026-07-08T08:11:00.000Z","7.0.2","6.2","7.4",[54,55,56,57,58],"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.2.3.zip",96,3,"2024-07-09 00:00:00",{"slug":65,"name":66,"version":67,"author":68,"author_profile":69,"description":70,"short_description":71,"active_installs":72,"downloaded":73,"rating":13,"num_ratings":34,"last_updated":74,"tested_up_to":75,"requires_at_least":76,"requires_php":18,"tags":77,"homepage":79,"download_link":80,"security_score":81,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"beyond-pay-for-woocommerce","Beyond Pay for WooCommerce","1.7.2","Beyond Pay","https:\u002F\u002Fprofiles.wordpress.org\u002Fbeyondpay\u002F","\u003Cp>\u003Cstrong>Warning: This plugin has been discontinued and should not be used for new installations. For additional information please refer to this \u003Ca href=\"https:\u002F\u002Fwww.globalpayments.com\u002Finsights\u002F2024\u002F11\u002F01\u002Fbeyond-developer-portal-retirement\" rel=\"nofollow ugc\">FAQ\u003C\u002Fa>. If further assistance is needed please contact Client Support at 888-480-1571, option 2.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Securely accept credit cards directly on your \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\" rel=\"nofollow ugc\">WooCommerce\u003C\u002Fa> store using \u003Ca href=\"https:\u002F\u002Fgetbeyond.com\" rel=\"nofollow ugc\">Beyond\u003C\u002Fa> with this \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002F\" rel=\"ugc\">WordPress\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Accept Visa, MasterCard, American Express, Discover, JCB, and Diners Club brand cards directly on your website\u003C\u002Fli>\n\u003Cli>No redirect to a third-party hosted payment page, reducing checkout friction and cart abandonment\u003C\u002Fli>\n\u003Cli>Card data is securely captured with Beyond Pay Gateway’s hosted payment fields presented via inline frame (iframe) and tokenized before reaching your server\u003C\u002Fli>\n\u003Cli>Recurring billing integration with the \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002Fproducts\u002Fwoocommerce-subscriptions\u002F\" rel=\"nofollow ugc\">WooCommerce Subscriptions Extension\u003C\u002Fa>. Beyond Pay for WooCommerce subscription features include the ability for customers to store or change their cards on file, cancel\u002Fsuspend\u002Freactivate subscriptions, and modify subscription amounts and due dates.\u003C\u002Fli>\n\u003Cli>Simplifies merchant PCI compliance obligations to the shorter \u003Ca href=\"https:\u002F\u002Fwww.pcisecuritystandards.org\u002Fpci_security\u002Fcompleting_self_assessment\" rel=\"nofollow ugc\">Self-Assessment Questionnaire “A” (SAQ-A)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Support either pre-authorization and later capture when WooCommerce order status changes, or authorization and capture at once (the combined “sale” transaction type)\u003C\u002Fli>\n\u003Cli>Optimize B2B card acceptance costs by automatically sending additional transaction data elements (also known as \u003Ca href=\"https:\u002F\u002Fwww.getbeyond.com\u002Fb2b-payments\u002F\" rel=\"nofollow ugc\">“Level II” and “Level III” information\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Issue refunds directly from the Order Details screen\u003C\u002Fli>\n\u003Cli>Custom CSS styling support for the hosted payment fields so you can create your ideal checkout experience\u003C\u002Fli>\n\u003Cli>Customizable gateway response and error messaging\u003C\u002Fli>\n\u003Cli>Test\u002Fsandbox mode for development and staging\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Configuration\u003C\u002Fh3>\n\u003Col>\n\u003Cli>From your WordPress \u003Cstrong>\u002Fwp-admin\u003C\u002Fstrong> page, navigate to \u003Cstrong>WooCommerce > Settings\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Select the \u003Cstrong>Payments\u003C\u002Fstrong> tab at the top of the screen.\u003C\u002Fli>\n\u003Cli>Click the \u003Cstrong>Manage\u003C\u002Fstrong> button for the Beyond Pay Gateway payment method.\u003C\u002Fli>\n\u003Cli>Proceed to configure payment method options available on this page:\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable\u002FDisable\u003C\u002Fstrong> – toggle to control whether this payment method is enabled or disabled\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Title\u003C\u002Fstrong> – this controls how this payment method is listed to the consumer during checkout; defaults to “Credit\u002FDebit Card”\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Description\u003C\u002Fstrong> – expanded description of this payment method when selected by consumer; defaults to “Pay with your credit or debit card.”\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detailed Error Messages\u003C\u002Fstrong> – controls the message returned to the consumer when there is a problem with their payment; defaults to “Something went wrong: %S. Please try again.” where \u003Cstrong>%S\u003C\u002Fstrong> represents the \u003Ca href=\"https:\u002F\u002Fdeveloper.getbeyond.com\u002F#gateway-result-codes\" rel=\"nofollow ugc\">raw response or error message\u003C\u002Fa> returned by the gateway\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable Test Mode\u003C\u002Fstrong> – controls whether transactions are sent to the Test\u002FSandbox or the Live\u002FProduction Beyond Pay Gateway environment and which type of API keys are expected; defaults to Live\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Username, Password, PublicKey, PrivateKey, MerchantCode,\u003C\u002Fstrong> and \u003Cstrong>MerchantAccountCode\u003C\u002Fstrong> – these are the credentials by which the plugin authenticates to the Beyond Pay Gateway in order to process payments; for Test Mode, you can \u003Ca href=\"https:\u002F\u002Fforms.office.com\u002Fpages\u002Fresponsepage.aspx?id=Q9V6UxGq3USJSkGsz2Jk7yRG7q939HJFkFXKp4lfZo1UMVBQWVNYSFBBNzJEV1k4Uko5WUU2NllBSCQlQCN0PWcu\" rel=\"nofollow ugc\">request Beyond Pay Gateway sandbox API keys\u003C\u002Fa> while live credentials are provided by Beyond once the merchant processing account is approved\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Transaction Mode\u003C\u002Fstrong> – controls how authorizations and payment captures are managed\u003C\u002Fli>\n\u003Cli>Set this to \u003Cstrong>\u003Cem>Authorization\u003C\u002Fem>\u003C\u002Fstrong> to perform only an authorization (“pre-auth”) when an order is placed which requires the Order Status to be changed to \u003Cstrong>Completed\u003C\u002Fstrong> in order for the payment to be captured (usually when an order is shipped)\u003C\u002Fli>\n\u003Cli>Set this to \u003Cstrong>\u003Cem>Sale\u003C\u002Fem>\u003C\u002Fstrong> to authorize and capture the payment immediately (usually used for digital products)\u003C\u002Fli>\n\u003Cli>Learn more about best practices for authorization and capture\u002Fsettlement from the \u003Ca href=\"https:\u002F\u002Fusa.visa.com\u002Fdam\u002FVCOM\u002Fdownload\u002Fmerchants\u002Fvisa-risk-management-guide-ecommerce.pdf\" rel=\"nofollow ugc\">Visa E-Commerce Risk Management Best Practices document\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Level II\u002FIII Data\u003C\u002Fstrong> – controls which extended data elements are automatically sent with transaction requests in order to \u003Ca href=\"https:\u002F\u002Fwww.getbeyond.com\u002Fb2b-payments\u002F\" rel=\"nofollow ugc\">optimize interchange rates on B2B cards\u003C\u002Fa>; Level II includes reference number and tax amount, while Level III includes line-item details. Set to Level III to ensure you always qualify for the best rates on eligible corporate purchasing cards. (Tax-exempt transactions are not eligible for Level II interchange rates but may be eligibile for Level III.)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Advanced Styling\u003C\u002Fstrong> – allows for customized styling of the Beyond Pay card collection iframe via CSS\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Verbose Logging\u003C\u002Fstrong> – enable for troubleshooting or development in order to log the gateway request and response messages on the Order Detail page; sensitive authentication details are not logged nor is any card data ever stored\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Click the \u003Cstrong>Save Changes\u003C\u002Fstrong> button once you have completed configuration; the page will refresh and a message reading “Your settings have been saved” will display at the top.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>You are now ready to accept payments through Beyond Pay Gateway on your WooCommerce store!\u003C\u002Fp>\n\u003Ch3>WooCommerce Subscriptions Integration\u003C\u002Fh3>\n\u003Cp>Beyond Pay for WooCommerce offers automated recurring billing functionality through integration with the official \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002Fproducts\u002Fwoocommerce-subscriptions\u002F\" rel=\"nofollow ugc\">WooCommerce Subscriptions Extension\u003C\u002Fa>. The Subscriptions Extension must be purchased from WooCommerce before recurring payments can be accepted with Beyond Pay for WooCommerce.\u003C\u002Fp>\n\u003Cp>Setting up your subscriptions is simple:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Create a subscription product in the Products module of WooCommerce and define the price and terms: e.g., “$5.90 every 2nd month”.\u003C\u002Fli>\n\u003Cli>As customers purchase subscription products on your store, they will be prompted to create a user account and save their payment method on file.\u003C\u002Fli>\n\u003Cli>When the payment is due, Beyond Pay for WooCommerce will automatically charge the card on file without you having to do anything.\u003C\u002Fli>\n\u003Cli>The status of each scheduled payment is reported back to your WooCommerce Subscription extension in WooCommerce, whether successful or failed.\u003C\u002Fli>\n\u003Cli>Your customers can change their payment method on the WooCommerce “my-account”  page. Here, customers can also click the “Renew Now” button and pay their subscription ahead of the due date.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>All card on file data is securely tokenized by Beyond Pay and never touches your server.\u003C\u002Fp>\n","Securely accept credit card payments using Beyond Pay gateway and optimize your cost of acceptance on B2B\u002Fcorporate cards.",40,3189,"2024-11-07T16:22:00.000Z","6.1.10","4.7",[20,78,21,56,24],"payment","https:\u002F\u002Fdeveloper.getbeyond.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbeyond-pay-for-woocommerce.zip",92,{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":92,"num_ratings":93,"last_updated":94,"tested_up_to":50,"requires_at_least":95,"requires_php":96,"tags":97,"homepage":100,"download_link":101,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"woo-authorize-net-gateway-aim","Secure Gateway for Authorize.net and WooCommerce by Pledged Plugins","6.1.26","mohsin.id","https:\u002F\u002Fprofiles.wordpress.org\u002Fmohsinoffline\u002F","\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.authorize.net\u002F\" rel=\"nofollow ugc\">Authorize.net\u003C\u002Fa> Payment Gateway for \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002F\" rel=\"nofollow ugc\">WooCommerce\u003C\u002Fa> allows you to accept credit cards payments into your Authorize.net merchant account from all over the world on your websites.\u003C\u002Fp>\n\u003Cp>WooCommerce is one of the oldest and most powerful e-commerce solutions for WordPress. This platform is very widely supported in the WordPress community which makes it easy for even an entry level e-commerce entrepreneur to learn to use and modify.\u003C\u002Fp>\n\u003Ch4>FREE Pro Version Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Easy Install\u003C\u002Fstrong>: Like all Pledged Plugins add-ons, this plugin installs with one click. After installing, you will have only a few fields to fill out before you are ready to accept credit cards on your store.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Secure Credit Card Processing\u003C\u002Fstrong>: Uses \u003Ca href=\"https:\u002F\u002Fdeveloper.authorize.net\u002Fapi\u002Freference\u002Ffeatures\u002Facceptjs.html\" rel=\"nofollow ugc\">Accept.js\u003C\u002Fa> library to send secure payment data directly to Authorize.net to reduce the PCI scope.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Refund via Dashboard\u003C\u002Fstrong>: Process full or partial refunds, directly from your WordPress dashboard! No need to search order in your Authorize.net account.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Authorize Now, Capture Later\u003C\u002Fstrong>: Optionally choose only to authorize transactions, and capture at a later date.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Restrict Card Types\u003C\u002Fstrong>: Optionally choose to restrict certain card types and the plugin will hide its icon and provide a proper error message on checkout.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gateway Receipts\u003C\u002Fstrong>: Optionally choose to send receipts from your Authorize.net merchant account.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Logging\u003C\u002Fstrong>: Enable logging so you can debug issues that arise if any.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Ch4>Enterprise Version Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Process Subscriptions:\u003C\u002Fstrong>  Use with  \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002Fproducts\u002Fwoocommerce-subscriptions\u002F\" rel=\"nofollow ugc\">WooCommerce Subscriptions\u003C\u002Fa>  extension to \u003Cstrong>create and manage products with recurring payments\u003C\u002Fstrong>  — payments that will give you residual revenue you can track and count on.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Setup Pre-Orders:\u003C\u002Fstrong>  Use with  \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002Fproducts\u002Fwoocommerce-pre-orders\u002F\" rel=\"nofollow ugc\">WooCommerce Pre-Orders\u003C\u002Fa>  extension so customers can order products before they’re available by submitting their card details. The card is then automatically charged when the pre-order is available.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Pay via Saved Cards:\u003C\u002Fstrong> Enable option to use saved card details on the gateway servers for quicker checkout. No sensitive card data is stored on the website!\u003C\u002Fli>\n\u003Cli>\u003Cstrong>ACH Payments:\u003C\u002Fstrong> Fully supports eCheck payments via ACH network.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>One Click Upsells:\u003C\u002Fstrong> Compatible with \u003Ca href=\"https:\u002F\u002Ffunnelkit.com\u002Fwoocommerce-one-click-upsells-upstroke\u002F\" rel=\"nofollow ugc\">FunnelKit (formerly WooFunnels) One Click Upsells\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fpledgedplugins.com\u002Fproducts\u002Fauthorize-net-payment-gateway-woocommerce\u002F\" rel=\"nofollow ugc\">Click here\u003C\u002Fa> for Pricing details.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>Requirements\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Active  \u003Ca href=\"https:\u002F\u002Fwww.authorize.net\u002F\" rel=\"nofollow ugc\">Authorize.net\u003C\u002Fa>  account – Sign up for a sandbox account  \u003Ca href=\"https:\u002F\u002Fdeveloper.authorize.net\u002Fhello_world\u002Fsandbox.html\" rel=\"nofollow ugc\">here\u003C\u002Fa>  if you need to test.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002F\" rel=\"nofollow ugc\">\u003Cstrong>WooCommerce\u003C\u002Fstrong>\u003C\u002Fa>  version 3.3 or later.\u003C\u002Fli>\n\u003Cli>A valid SSL certificate is required to ensure your customer credit card details are safe and make your site PCI DSS compliant. This plugin does not store the customer credit card numbers or sensitive information on your website.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Extend, Contribute, Integrate\u003C\u002Fh4>\n\u003Cp>Visit the \u003Ca href=\"https:\u002F\u002Fpledgedplugins.com\u002Fproducts\u002Fauthorize-net-payment-gateway-woocommerce\u002F\" rel=\"nofollow ugc\">plugin page\u003C\u002Fa> for more details. Contributors are welcome to send pull requests via \u003Ca href=\"https:\u002F\u002Fbitbucket.org\u002Fpledged\u002Fwc-authorize.net-pro\u002F\" rel=\"nofollow ugc\">Bitbucket repository\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>For custom payment gateway integration with your WordPress website, please \u003Ca href=\"https:\u002F\u002Fwpgateways.com\u002Fsupport\u002Fcustom-payment-gateway-integration\u002F\" rel=\"nofollow ugc\">contact us here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Disclaimer\u003C\u002Fh4>\n\u003Cp>This plugin is not affiliated with or supported by Authorize.net, WooCommerce.com or Automattic. All logos and trademarks are the property of their respective owners.\u003C\u002Fp>\n","Authorize.net payment gateway integration for WooCommerce to accept credit cards directly on WordPress e-commerce websites.",10000,419786,98,34,"2026-04-27T17:53:00.000Z","4.4","5.6",[98,21,99,56,24],"authorize-net","pci","https:\u002F\u002Fpledgedplugins.com\u002Fproducts\u002Fauthorize-net-payment-gateway-woocommerce\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwoo-authorize-net-gateway-aim.6.1.26.zip",{"slug":103,"name":104,"version":105,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":110,"downloaded":111,"rating":112,"num_ratings":113,"last_updated":114,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":115,"homepage":117,"download_link":118,"security_score":13,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"woo-asaas","Asaas Gateway for WooCommerce","2.7.7","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.",8000,192594,84,23,"2026-05-22T13:20:00.000Z",[116,20,78,21,24],"asaas","https:\u002F\u002Fwww.asaas.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwoo-asaas.2.7.7.zip",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":127,"downloaded":128,"rating":61,"num_ratings":129,"last_updated":130,"tested_up_to":131,"requires_at_least":132,"requires_php":133,"tags":134,"homepage":137,"download_link":138,"security_score":13,"vuln_count":139,"unpatched_count":27,"last_vuln_date":140,"fetched_at":29},"woo-vipps","Pay with Vipps and MobilePay for WooCommerce","6.0.5","WP Hosting AS","https:\u002F\u002Fprofiles.wordpress.org\u002Fwphostingdev\u002F","\u003Cp>\u003Cem>Official Vipps MobilePay payment plugin for WooCommerce. Let your Norwegian, Danish, and Finnish customers pay with Vipps and MobilePay for an easy, fast, and familiar shopping experience\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Vipps is used by more than 93 % of Norway’s population (4.2 million users).\u003C\u002Fp>\n\u003Cp>MobilePay is used by more than 92 % of Denmark’s population (4.4 million users), and approximately 59 % of Finland’s population (2.8 million users).\u003C\u002Fp>\n\u003Cp>Vipps and MobilePay are payment methods offered by Vipps MobilePay.\u003C\u002Fp>\n\u003Cp>When you enable this plugin, you will choose between offering either Vipps or MobilePay as a payment method for your customers – hence “Vipps\u002FMobilePay” going forward.\u003C\u002Fp>\n\u003Cp>This is the official plugin for Vipps\u002FMobilePay ePayments (\u003Cem>Vipps Nettbetaling\u003C\u002Fem>), Vipps MobilePay Express (\u003Cem>Vipps MobilePay Hurtigkasse\u003C\u002Fem>) and Vipps\u002FMobilePay recurring payments. Increase your conversion rate by letting your customers choose Vipps\u002FMobilePay directly in the checkout or even do an Express Checkout (Vipps only) from the cart or a product page directly.\u003C\u002Fp>\n\u003Cp>You can also do important back office tasks such as capture and refund directly from WooCommerce. Easy for your customer and easy for you.\u003C\u002Fp>\n\u003Cp>Read \u003Ca href=\"https:\u002F\u002Fdeveloper.vippsmobilepay.com\u002Fdocs\u002Fplugins\u002Fwoocommerce\u002F\" rel=\"nofollow ugc\">information from Vipps MobilePay\u003C\u002Fa> about the plugin.\u003C\u002Fp>\n\u003Ch3>Vipps\u002FMobilePay ePayment\u003C\u002Fh3>\n\u003Cp>When you enable this plugin, your customers will be able to choose Vipps\u002FMobilePay as a payment method in the checkout. There is no need to go via a third party payment method. If your customer choose Vipps\u002FMobilePay, they fill in their name and address and is then asked to enter their phone number in the Vipps\u002FMobilePay dialogue. They then confirms the payment in the Vipps\u002FMobilePay app. Customer info like name and address is sent to the store from Vipps MobilePay.\u003C\u002Fp>\n\u003Ch3>Vipps\u002FMobilePay recurring payments\u003C\u002Fh3>\n\u003Cp>Vipps\u002FMobilePay recurring payments is perfect for you if you run a web shop with subscription based services or other products that would benefit from subscriptions.\u003C\u002Fp>\n\u003Cp>With Vipps\u002FMobilePay recurring payments you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Sell recurring products (virtual and physical)\u003C\u002Fli>\n\u003Cli>Offer subscription services\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fdeveloper.vippsmobilepay.com\u002Fdocs\u002FAPIs\u002Frecurring-api\u002Fhow-it-works\u002F\" rel=\"nofollow ugc\">How it works\u003C\u002Fa> for an overview.\u003C\u002Fp>\n\u003Cp>Recurring payments requires \u003Ca href=\"https:\u002F\u002Fwoocommerce.com\u002Fproducts\u002Fwoocommerce-subscriptions\u002F\" rel=\"nofollow ugc\">WooCommerce Subscriptions\u003C\u002Fa> and a Vipps MobilePay MSN with recurring payments added.\u003C\u002Fp>\n\u003Ch3>MobilePay Reservations are currently for 14 days\u003C\u002Fh3>\n\u003Cp>When a payment is completed with Vipps MobilePay, the money will be reserved, but only transferred to the merchant when the order is set to “Complete” or the money is captured manually. \u003Cem>For MobilePay, this reservation period is 14 days\u003C\u002Fem>, so you will need to ship and fulfill orders before this; or to make an agreement with the customer to capture the money before this period is over. For Vipps, the period is 180 days. For payments made by credit card in Vipps\u002FMobilePay Checkout, the period can again be as short as 7 days.\u003Cbr \u002F>\nFor details, please read the \u003Ca href=\"https:\u002F\u002Fdeveloper.vippsmobilepay.com\u002Fdocs\u002Fknowledge-base\u002Freserve-and-capture\u002F#reserve-and-capture-faq\" rel=\"nofollow ugc\">developer FAQ\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If the order only contains virtual and downloadable products, the plugin will capture the order automatically and set the order to “Completed” as is the standard WooCommerce rule.\u003C\u002Fp>\n\u003Ch3>Vipps MobilePay Express\u003C\u002Fh3>\n\u003Cp>When you enable Vipps MobilePay Express, your customers can choose between the regular checkout or to go directly to Vipps or MobilePay. If they choose Vipps or MobilePay, they just submit their phone number, and the rest of the checkout process is done in the Vipps or MobilePay app.\u003C\u002Fp>\n\u003Cp>Since Vipps MobilePay knows who the customers are, they don’t have to enter all their personal information. The customer just choose the shipping method and accepts the payment. Vipps MobilePay will send all the necessary info back to the store. Easy, fast and secure.\u003C\u002Fp>\n\u003Cp>The express checkout can be done in the following ways:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>From the cart\u003C\u002Fli>\n\u003Cli>From the category pages\u003C\u002Fli>\n\u003Cli>From the product page\u003C\u002Fli>\n\u003Cli>From shareable links distributed by email, banners, etc.\u003C\u002Fli>\n\u003Cli>From QR codes distributed digitally or in print\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Settings for the cart, category and product pages can be found in the WooCommerce settings for the Vipps MobilePay payment gateway.\u003C\u002Fp>\n\u003Cp>Shareable links and QR codes can be generated from the Vipps\u002FMobilePay tab on the product page.\u003C\u002Fp>\n\u003Ch3>Vipps MobilePay Checkout\u003C\u002Fh3>\n\u003Cp>With Checkout enabled in the plugin, you will get a complete checkout in your web shop, designed and run by Vipps MobilePay.\u003Cbr \u002F>\nYour customers can pay with Vipps, MobilePay, VISA or MasterCard, and they can also provide their shipping address and choose their preferred shipping method in a simple manner.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Checkout – important update\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Vipps MobilePay has entered into an agreement to sell the Vipps MobilePay Checkout solution to \u003Ca href=\"https:\u002F\u002Fwww.kustom.co\u002F\" rel=\"nofollow ugc\">Kustom\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>As part of this transition, \u003Cem>Vipps MobilePay Checkout\u003C\u002Fem> will become \u003Cem>Kustom Checkout\u003C\u002Fem>. This means the Checkout product you ordered will be delivered and developed by Kustom going forward.\u003Cbr \u002F>\nIf you have questions, you can check our \u003Ca href=\"https:\u002F\u002Fvippsmobilepay.com\u002Fvippsmobilepay-kustom\" rel=\"nofollow ugc\">FAQ\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>How to get started\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Sign up in the \u003Ca href=\"https:\u002F\u002Fportal.vippsmobilepay.com\" rel=\"nofollow ugc\">Vipps MobilePay portal\u003C\u002Fa> and choose your product.\u003C\u002Fli>\n\u003Cli>After 1-2 days you will get an email with login details to Vipps MobilePay Business Portal, where you can get the API credentials\u003C\u002Fli>\n\u003Cli>Download and install the plugin\u003C\u002Fli>\n\u003Cli>Configure the plugin\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How to install the plugin\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Install the plugin using WordPress’ \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FManaging_Plugins#Installing_Plugins\" rel=\"nofollow ugc\">built-in installer\u003C\u002Fa>. The plugin can also be installed manually by upload the plugin files to the \u002Fwp-content\u002Fplugins\u002F directory.\u003C\u002Fli>\n\u003Cli>Activate the plugin through the ‘Plugins’ screen in WordPress.\u003C\u002Fli>\n\u003Cli>Go to the WooCommerce Settings page and choose Payment Gateways (Betalinger) and enable Vipps\u002FMobilePay.\u003C\u002Fli>\n\u003Cli>Go the settings page for the Vipps MobilePay plugin and enter your Vipps MobilePay account keys. Your account keys are available in the Vipps Business Portal (detailed info in the section below)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>How to get Vipps MobilePay account keys from Vipps MobilePay Business Portal\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Sign in to the Vipps MobilePay Portal at \u003Ca href=\"https:\u002F\u002Fportal.vippsmobilepay.com\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fportal.vippsmobilepay.com\u002F\u003C\u002Fa> using Bank ID\u003C\u002Fli>\n\u003Cli>Select the “Utvikler” (“Developer”) tab and choose Production Keys. Here you can find the merchant serial number (6 figures)\u003C\u002Fli>\n\u003Cli>Click on “Show keys” under the API keys column to see “Client ID”, “Client Secret” and “Vipps MobilePay Subscription Key”\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Contributing on Github\u003C\u002Fh3>\n\u003Cp>This project is hosted on Github at: https:\u002F\u002Fgithub.com\u002Fvippsas\u002Fvipps-woocommerce\u003C\u002Fp>\n\u003Ch3>Extending the Order Management API integration\u003C\u002Fh3>\n\u003Cp>From version 1.10.0, this plugin implements the Vipps MobilePay Order Management API, sending a receipt to the customers’ app, and sending the order confirmation link as the Order Confirmation link category.  You can, using this api, send over an image and a link for the categories receipt (RECEIPT), ticket (TICKET), shipping (DELIVERY), booking (BOOKING) and a general category (GENERAL).\u003C\u002Fp>\n\u003Cp>For instance, if you have a page or url for tracking shipping, you can add this to the customers’ app by extending the ‘woo_vipps_add_order_categories’ filter like so:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>   add_filter('woo_vipps_add_order_categories', function ($categories, $order, $gateway) {\n          $shippingpagedata = array(\n            'link' => \u003Cyour shipping URL here>, \n            'image' => \u003Cfilename or attachment ID of your illustration for shipping here, if required>,\n            'imagesize' => \u003Cfor attachments, the image size to use>);\n          $categories['DELIVERY'] = $shippingpagedata;\n          return $categories;\n      }, 10, 3);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can similarily send ticket information (with e.g. a QR code) for the TICKET or BOOKING category and so forth.\u003C\u002Fp>\n\u003Ch4>Javascript filters and actions\u003C\u002Fh4>\n\u003Cp>From version 1.1.13 you can also modify the javascript using the new WP hooks library for javascript:\u003Cbr \u002F>\n * ‘vippsBuySingleProduct’ – action which is run whenever a customer tries to buy a single product using express checkout\u003Cbr \u002F>\n * ‘vippsBuySingleProductCompatMode’ – filter which should return true or false, if true, the compatibility mode action will be run instead of the standard ajax.\u003Cbr \u002F>\n * ‘vippsBuySingleProductCompatModeAction’ – filter which should return a javascript function to run when buying a product and compatibility mode is on. Will normally press the “Buy” button for you.\u003Cbr \u002F>\n * ‘vippsRemoveErrorMessages’ – runs when Vipps MobilePay error messages are to be removed.\u003Cbr \u002F>\n * ‘vippsErrorMessage’ – runs for every Vipps MobilePay error message added with Javascript. Takes the message as an argument\u003Cbr \u002F>\n * ‘vippsAddErrorMessage’ – runs when an error message is about to be added. Takes the message as an argument\u003Cbr \u002F>\n * ‘vippsInit’  – runs when a page with a Vipps MobilePay button is initialzed\u003Cbr \u002F>\n * ‘vippsStatusCheckErrorHandler’ – A filter that should return function taking a statustext and an error object. It receives the default error handler, and is called when checking the order status with ajax for some reason ends up in an error.\u003C\u002Fp>\n","Official Vipps MobilePay payment plugin for WooCommerce.",5000,497811,13,"2026-06-24T06:49:00.000Z","7.0.0","6.3","8.0",[135,22,56,136,24],"mobilepay","vipps","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwoo-vipps\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwoo-vipps.6.0.5.zip",1,"2023-12-27 00:00:00",{"attackSurface":142,"codeSignals":190,"taintFlows":205,"riskAssessment":206,"analyzedAt":214},{"hooks":143,"ajaxHandlers":186,"restRoutes":187,"shortcodes":188,"cronEvents":189,"entryPointCount":27,"unprotectedCount":27},[144,150,153,158,162,166,170,174,178,182],{"type":145,"name":146,"callback":147,"priority":27,"file":148,"line":149},"action","plugins_loaded","rpgwcc_gateway_init","recurring-payment-woo-ccbill.php",20,{"type":145,"name":151,"callback":152,"file":148,"line":113},"admin_notices","rpgwcc_check_woocommerce_subscriptions",{"type":154,"name":155,"callback":156,"priority":11,"file":148,"line":157},"filter","woocommerce_add_to_cart_validation","rpgwcc_woo_subscription_check",35,{"type":145,"name":159,"callback":160,"file":148,"line":161},"rpgwcc_valid_ipn_request","successful_request",130,{"type":145,"name":163,"callback":164,"file":148,"line":165},"woocommerce_receipt_ccbill","receipt_page",131,{"type":145,"name":167,"callback":168,"file":148,"line":169},"woocommerce_update_options_payment_gateways","process_admin_options",132,{"type":145,"name":171,"callback":172,"file":148,"line":173},"woocommerce_api_wc_gateway_ccbill_payment_gateway","check_ipn_response",134,{"type":154,"name":175,"callback":176,"file":148,"line":177},"woocommerce_payment_gateways","add_rpgwcc_gateway",619,{"type":145,"name":179,"callback":180,"priority":11,"file":148,"line":181},"woocommerce_subscription_status_updated","wc_subscription_cancelled_notify_ccbill",645,{"type":154,"name":183,"callback":184,"priority":11,"file":148,"line":185},"woocommerce_get_settings_checkout","rpgwcc_add_instructions",703,[],[],[],[],{"dangerousFunctions":191,"sqlUsage":192,"outputEscaping":194,"fileOperations":27,"externalRequests":139,"nonceChecks":139,"capabilityChecks":139,"bundledLibraries":204},[],{"prepared":27,"raw":27,"locations":193},[],{"escaped":195,"rawEcho":62,"locations":196},11,[197,200,202],{"file":148,"line":198,"context":199},150,"raw output",{"file":148,"line":201,"context":199},151,{"file":148,"line":203,"context":199},438,[],[],{"summary":207,"deductions":208},"The plugin \"recurring-payment-woo-ccbill\" v1.0 exhibits a generally strong security posture based on the provided static analysis. The complete absence of AJAX handlers, REST API routes, shortcodes, and cron events as entry points significantly limits the plugin's attack surface. Furthermore, the code signals indicate good development practices, with all SQL queries utilizing prepared statements and a high percentage of output escaping. The presence of nonce and capability checks also suggests an awareness of security best practices for WordPress.\n\nHowever, a minor concern arises from the single external HTTP request, which, if not handled with proper validation and sanitization on the receiving end, could potentially be a vector for vulnerabilities. The 21% of improperly escaped output, while not critical in this specific scan, represents a potential risk for cross-site scripting (XSS) vulnerabilities in future updates or if the plugin interacts with user-provided data in ways not apparent in this static analysis. The lack of any recorded vulnerabilities in its history is a positive sign, suggesting either a well-developed plugin or a relatively new one with limited exposure. Overall, this plugin appears to be built with security in mind, but vigilance is recommended regarding external interactions and output sanitization.",[209,211],{"reason":210,"points":62},"1 external HTTP request",{"reason":212,"points":213},"21% of outputs not properly escaped",5,"2026-03-17T00:01:05.588Z",{"wat":216,"direct":227},{"assetPaths":217,"generatorPatterns":221,"scriptPaths":222,"versionParams":223},[218,219,220],"\u002Fwp-content\u002Fplugins\u002Frecurring-payment-woo-ccbill\u002Fcss\u002Frpgwcc_style.css","\u002Fwp-content\u002Fplugins\u002Frecurring-payment-woo-ccbill\u002Fjs\u002Frpgwcc_script.js","\u002Fwp-content\u002Fplugins\u002Frecurring-payment-woo-ccbill\u002Fjs\u002Frpgwcc_validate.js",[],[219,220],[224,225,226],"recurring-payment-woo-ccbill\u002Fcss\u002Frpgwcc_style.css?ver=","recurring-payment-woo-ccbill\u002Fjs\u002Frpgwcc_script.js?ver=","recurring-payment-woo-ccbill\u002Fjs\u002Frpgwcc_validate.js?ver=",{"cssClasses":228,"htmlComments":230,"htmlAttributes":231,"restEndpoints":233,"jsGlobals":235,"shortcodeOutput":237},[229],"rpgwcc-notice",[],[232],"data-tip=\"The ID of the CCBill FlexForm used to collect payment\"",[234],"\u002Fwp-json\u002Fwc\u002Fv3\u002Forders",[236],"RPGWCC_Gateway",[],{"error":239,"url":240,"statusCode":241,"statusMessage":242,"message":242},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Frecurring-payment-woo-ccbill\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":34,"versions":244},[245,251],{"version":6,"download_url":26,"svn_tag_url":246,"released_at":28,"has_diff":247,"diff_files_changed":248,"diff_lines":28,"trac_diff_url":249,"vulnerabilities":250,"is_current":239},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Frecurring-payment-woo-ccbill\u002Ftags\u002F1.1.0\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Frecurring-payment-woo-ccbill%2Ftags%2F1.0&new_path=%2Frecurring-payment-woo-ccbill%2Ftags%2F1.1.0",[],{"version":252,"download_url":253,"svn_tag_url":254,"released_at":28,"has_diff":247,"diff_files_changed":255,"diff_lines":28,"trac_diff_url":28,"vulnerabilities":256,"is_current":247},"1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frecurring-payment-woo-ccbill.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Frecurring-payment-woo-ccbill\u002Ftags\u002F1.0\u002F",[],[]]