Please consider adding support for taking MOTO payments via Stripe directly against WooCommerce orders created/managed in admin. Ideal workflow: create/edit order in admin take payment while on the phone with the customer process it correctly as a MOTO transaction keep everything tied neatly to the Woo order for refunds, order notes, and reconciliation This would make Stripe a strong option for admin-side phone order workflows and provide a much smoother experience than relying on a separate virtual terminal for those that already use Stripe. Stripe appears to support the underlying MOTO/manual-entry capability, so it would be great to see that exposed in the plugin in a WooCommerce-friendly way. https://docs.stripe.com/terminal/features/mail-telephone-orders/payments?locale=en-GB https://support.stripe.com/questions/when-to-categorize-transactions-as-mail-order-telephone-order-%28moto%29 Best regards
In prior ecommerce systems it has been very helpful to have the type of Payment card used and last 4 digits of the cart shown on the order confirmation and in the the backend admin. Is there any way to add this functionality>> Using AG 4.0.0 Server.
FunnelKit, One-Click Upsell and SagePay compatibility. (Opayo Direct)
Could you add the option to display Discover, Applepay and GooglePay logos in AG AIB Authipay please?
We use Server integration with our current Magento website, which means we do not need to deal with PCI issues. It would be fantastic if Server integration in the WeareAG Woocommerce module could also support server integration.
Problem with PayPal (Auth/Capture) functionality. Payone told us, that we need to change your plugin to send a different "requiresApproval" value: https://developer.payone.com/en/payment-methods-and-features/payment-methods/paypal Because we need to send "false" to automatically capture the payment. We set "OPERATION" (woocommerceagwlhcheckoutoperation) to SALE in your settings. But that does not work.
This plugin works great with Opayo Pi on the normal version of Woocommerce checkout, however, it would be great if this plugin worked with Opayo Pi as part of the new Woocommerce Checkout Blocks.
As checkouts are starting to move to checkout blocks, the ability to use the direct integration with blocks would be beneficial.
Allow customers to save card in their account page on the website.
Because of the highly customised order workflow on a merchant's website, there are instances where no actual orders require capture, but authentication for credit checks is still necessary. In such cases, having an "authorized/authenticated" status would be extremely beneficial.
Add a doaction call on paymentcomplete inside class-order.php so developers can hook into it to trigger further actions after a successful payment.
We are using your premium Opayo plugin and would like to ask whether you have any plans to support a more developer-friendly way to modify the $data array before it is sent to Opayo. In a previous (third-party) Opayo plugin we used, this was possible via filters. It allowed us to programmatically adjust values such as the transaction type (TxType), which is critical for our use case. We occasionally process transactions with a total of £0.00, and handling these requires modifying the data before submission. At the moment, your plugin doesn't appear to offer a clean way to do this without modifying core plugin files - something we want to avoid, especially with a premium product, as those changes are lost on updates.
We are using your premium Opayo plugin and would like to ask whether you have any plans to support a more developer-friendly way to modify the $data array before it is sent to Opayo. In a previous (third-party) Opayo plugin we used, this was possible via filters. It allowed us to programmatically adjust values such as the transaction type (TxType), which is critical for our use case. We occasionally process transactions with a total of £0.00, and handling these requires modifying the data before submission. At the moment, your plugin doesn't appear to offer a clean way to do this without modifying core plugin files - something we want to avoid, especially with a premium product, as those changes are lost on updates.
We are using the system to allow bookings from 2 different websites. This works well using prefixes on the invoice numbers - but at present we need to disable the webhooks to do so. After speaking to your developer, I believe this is something you're working on, but we could do with it ASAP.
It would allow our users to add the webhook to multiple website.
Since you now managed to achieve this with your Opayo plugin(https://we-are-ag.canny.io/feature-request/p/add-support-for-direct-and-pi-to-the-opayo-plugin), Stripe have had this forever in their WooCommerce plugin, and your already have the API support in the First Data Connect plugin, isn't it time to offer API payments direct in the WooCommerce checkout with your First Data Connect plugin? And since direct integration into the checkout is already in your Opayo plug-in and Stripe's plugin, you don't need to mention PCI compliance :) Thanks!
Since you now managed to achieve this with your Opayo plugin(https://we-are-ag.canny.io/feature-request/p/add-support-for-direct-and-pi-to-the-opayo-plugin), Stripe have had this forever in their WooCommerce plugin, and your already have the API support in the First Data Connect plugin, isn't it time to offer API payments direct in the WooCommerce checkout with your First Data Connect plugin? And since direct integration into the checkout is already in your Opayo plug-in and Stripe's plugin, you don't need to mention PCI compliance :) Thanks!