IDPay Payment Gateway For LearnPress vs WeeConnectPay – Clover Payment Gateway for WooCommerce

After installing and enabling this plugin, your customers can pay through IDPay gateway. For doing a transaction through IDPay gateway, you must have an API Key. You can obtain the API Key by going to your dashboard in your IDPay account. 1.1.0, Nov 13, 2022 Tested Up With WordPress 6.1 And LearnPress 4.1.7.3.2 Check Double Spending Correct Check Does Not Xss Attack Correct First Official Release 1.0.1, October 19, 2020 Support GET method in Callback. 1.0.0, July 14, 2020 Develope release.

WeeConnectPay connects your WooCommerce store to your Clover account. Shoppers pay by card or Google Pay without leaving your checkout, and every online sale lands in Clover next to your in-store sales, with the tax, stock, and order detail you choose to send along. Payments – Card details are entered in secure fields provided by Clover, directly on your checkout page, on both the Classic and Block-based checkout. Card numbers never pass through your site. – Google Pay express checkout, when enabled on your store. – Three transaction modes, named for what they do: Charge at checkout, Hold and charge later, and Order and charge, which also creates the matching order in your Clover dashboard. – Refunds from WooCommerce’s own Refund button, including several partial refunds on the same charge, with a note on the order for everything that happens. Clover reporting, taxes, and stock – Tax reporting: link your WooCommerce tax rates to your Clover rates, then choose what each payment reports to Clover: nothing, the total only, or each rate by name. – Stock sync: link your products to your Clover inventory items and choose a mode: Off, Preview only, Follow Clover, or Two-way. – Inventory Tools: move your catalog in bulk. Export WooCommerce products to Clover, or import Clover items into WooCommerce. – All of this is off until you turn it on, and none of it can ever block a payment. Day to day – Fully available in English and in French. – Clear notes on every order: what was charged, what was refunded, and the real reason when a card is declined. – A visible notice when your Clover connection needs attention, which clears itself once you reconnect. Doing business together Doing business with WeeConnectPay means being heard. The team that builds the plugin is the team that answers you, and requests from merchants like you regularly become features in the next update. WeeConnectPay requires a Clover merchant account. You can apply through WeeConnectPay, where you will also find pricing and documentation. Privacy and Data Collection Payment processing. As a payment gateway, this plugin sends checkout and order information (line items, amounts, taxes, and the customer details required to process the payment) to the WeeConnectPay service you connected during onboarding, which processes the payment through Clover. This is the service the plugin exists to provide. Error diagnostics (off by default). The plugin can send technical error reports to WeeConnectPay to help diagnose a problem on your store. This is disabled by default and only turns on when you ask WeeConnectPay support for help and a support agent opens a temporary diagnostic window for your store. The window expires automatically after at most 7 days and can be closed earlier by support on request. While the window is open, if the plugin’s own code encounters an error, a report is sent to WeeConnectPay containing: the technical error type and message, the location of the error inside this plugin’s files, and the plugin, WooCommerce, WordPress, and PHP version numbers. Error reports never include customer names, emails, addresses, order contents, payment details, cookies, or form submissions. When the window is closed or expired, nothing is sent. No analytics, usage tracking, or advertising data is ever collected. Bot protection (optional, off by default). If you turn on Google reCAPTCHA v3 in the plugin settings, your checkout page loads Google’s reCAPTCHA script (https://www.google.com/recaptcha/api.js) and Google assesses each checkout attempt. Google receives the shopper’s IP address, browser information, and interaction signals from the page, and returns a score the plugin uses to decide whether to let the payment through. Google’s handling of that data is covered by the Google Privacy Policy (https://policies.google.com/privacy) and the Google Terms of Service (https://policies.google.com/terms). Nothing is sent to Google when this setting is off, which is the default.