Or, does this need to be done through myCred? And, if I use myCred, do I also need to use Woocommerce as well?

So recently we processed an order, which we refunded on the 6th of November. However, on the 18th of November, we got a notification saying the refund had failed, and that the customer has started a dispute.

The thing, however, is that the money have already left the account. But I got an email recently which said I have to pay the refunded amount again. It shows that it failed on the website, but the money is already gone from the account. And some more will leave.

I have sent the customer a few emails over the course of last few weeks but they are unresponsive, so I can’t confirm if they have received it, or if there is another issue.

PHP Fatal error: Uncaught Error: Call to undefined function PaymentPlugins\\Stripe\\WooCommerceSubscriptions\\Controllers\\wcs_is_manual_renewal_enabled() in /var/www/fsf/wp-content/plugins/woo-stripe-payment/packages/subscriptions/src/Controllers/PaymentIntent.php:67

Stack trace:

#0 /var/www/fsf/wp-includes/class-wp-hook.php(324): PaymentPlugins\\Stripe\\WooCommerceSubscriptions\\Controllers\\PaymentIntent->is_subscription_mode(

#1 /var/www/fsf/wp-includes/plugin.php(205): WP_Hook->apply_filters()

#2 /var/www/fsf/wp-content/plugins/woo-stripe-payment/src/Controllers/PaymentIntent.php(118): apply_filters()

#3 /var/www/fsf/wp-content/plugins/woo-stripe-payment/src/Controllers/PaymentIntent.php(79): PaymentPlugins\\Stripe\\Controllers\\PaymentIntent->is_subscription_mode(

#4 /var/www/fsf/wp-content/plugins/woo-stripe-payment/includes/gateways/class-wc-payment-gateway-stripe-cc.php(164): PaymentPlugins\\Stripe\\Controllers\\PaymentIntent->get_element_options()

#5 /var/www/fsf/wp-content/plugins/woo-stripe-payment/packages/blocks/src/Payments/AbstractStripePayment.php(84): WC_Payment_Gateway_Stripe_CC->get_element_options()

#6 /var/www/fsf/wp-content/plugins/woo-stripe-payment/packages/blocks/src/Payments/Gateways/CreditCardPayment.php(60): PaymentPlugins\\Blocks\\Stripe\\Payments\\AbstractStripePayment->get_payment_method_data()

#7 /var/www/fsf/wp-content/plugins/woocommerce/src/Blocks/Payments/PaymentMethodRegistry.php(62): PaymentPlugins\\Blocks\\Stripe\\Payments\\Gateways\\CreditCardPayment->get_payment_method_data(

#8 /var/www/fsf/wp-content/plugins/woocommerce/src/Blocks/Payments/Api.php(92): Automattic\\WooCommerce\\Blocks\\Payments\\PaymentMethodRegistry->get_all_registered_script_data()

#9 /var/www/fsf/wp-includes/class-wp-hook.php(324): Automattic\\WooCommerce\\Blocks\\Payments\\Api->add_payment_method_script_data()

#10 /var/www/fsf/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#11 /var/www/fsf/wp-includes/plugin.php(517): WP_Hook->do_action()

#12 /var/www/fsf/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/Cart.php(265): do_action()

#13 /var/www/fsf/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/AbstractBlock.php(416): Automattic\\WooCommerce\\Blocks\\BlockTypes\\Cart->enqueue_data()

#14 /var/www/fsf/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/Cart.php(147): Automattic\\WooCommerce\\Blocks\\BlockTypes\\AbstractBlock->enqueue_assets()

#15 /var/www/fsf/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/AbstractBlock.php(96): Automattic\\WooCommerce\\Blocks\\BlockTypes\\Cart->enqueue_assets()

#16 /var/www/fsf/wp-includes/class-wp-block.php(537): Automattic\\WooCommerce\\Blocks\\BlockTypes\\AbstractBlock->render_callback()

#17 /var/www/fsf/wp-includes/blocks.php(2190): WP_Block->render()

#18 /var/www/fsf/wp-includes/blocks.php(2242): render_block()

#19 /var/www/fsf/wp-includes/class-wp-hook.php(324): do_blocks()

#20 /var/www/fsf/wp-includes/plugin.php(205): WP_Hook->apply_filters()

#21 /var/www/fsf/wp-includes/post-template.php(256): apply_filters()

#22 /var/www/fsf/wp-content/themes/Avada/page.php(24): the_content()

#23 /var/www/fsf/wp-includes/template-loader.php(106): include('...')

#24 /var/www/fsf/wp-blog-header.php(19): require_once('...')

#25 /var/www/fsf/index.php(17): require('...')

#26 {main} thrown in /var/www/fsf/wp-content/plugins/woo-stripe-payment/packages/subscriptions/src/Controllers/PaymentIntent.php on line 67, referer: https://fsf.com/my-account/

WordPress 6.7
Astra Theme 4.8.6
WooCommerce 9.4.1
and only WooCommerce Stripe Payment Plugin 8.9.0, following errors:

• After a payment without any other plugin, e.g. BACS, the thank you page not loading. Error: Session is expired (different pcs tested)
• In this combination I can’t update the cart (logged in, logged out, different pcs,…), it always stays the same e.g. 3 units of product xy!
  
  If the Plugin is disabled, all of the errors are gone…

I have the same problem as this person: https://www.ads-software.com/support/topic/random-orders-get-stuck-in-pending-payment-even-order-is-complete/, but the proposed solutions didn’t work.

To describe the problem we have 99% of orders no problem, but sometimes an order remains pending payment while the payment has been debited on stripe (and marked successful).
What can we do to stop the problem?

There are no payment methods available. This may be an error on our side. Please contact us if you need any help placing your order.

…I had tried previously to install Payment Gateway Plugin for PayPal WooCommerce but this also resulted in the same message above.

Currently I have only 4 plugins…

1. Regenerate ThumbnailsVersion 3.1.6 by Alex Mills (Viper007Bond) | Auto-updates enabled
2. WooCommerceVersion 9.3.3 by Automattic | Auto-updates enabled
3. WP-Optimize – Clean, Compress, CacheVersion 3.7.0 by TeamUpdraft, DavidAnderson | Auto-updates enabled
4. WP Go Maps (formerly WP Google Maps)Version 9.0.43 by WP Go Maps (formerly WP Google Maps) | Auto-updates enabled

…installed in WordPress 6.62

My site is so basic and minimal I can’t understand what could be wrong.

I need to have both:

• Events with reservations and payment gateways enabled. This is the functionality that would be added when enabling the PRO version of the plugin.
• Events with reservations enabled, and a price shown for information purposes, but no payment gateways enabled. Basically, have the same behavior that I have today without PRO version enabled.

Is there a way to have these two types of events in Events Manager PRO?

Thank you!

I’ve traced it in the logs and the problem appears to be on orders that use an exchange rate (our shop is in GBP, one order is in EUR and another is in USD) _and_ the PATCH request to https://api-m.paypal.com/v2/checkout/orders/... contains a breakdown.

Normally, there only appears to be a breakdown when it is in the default currency. All other foreign currency payments just PATCH the total, the shipping address and the invoice number. But the ones with the incorrect price contain a breakdown. And the breakdown contains the GBP price but with the currency set to the customer’s currency (e.g. a ￡10 item is in the breakdown as {"currency_code":"EUR","value":"10.00"} rather than {"currency_code":"EUR","value":"11.50"} (assuming an exchange rate of 1:1.15)

I can’t recreate this because I don’t know what triggered it. There’s no obvious difference between the orders. Customers ordering the same items in the same currency got charged correctly. Customers ordering different items got charged correctly. It was just these two orders.

We’re running the following additional WooCommerce plugins:

• Order Tip for WooCommerce
• WBW Currency Switcher for WooCommerce
• WooCommerce Shipping & Tax
• WooCommerce Weight Based Shipping

However, I don’t see how it can be any of those when other orders that also gave a tip, picked a currency, and used weight-based shipping were all okay.

My questions:

1. Is it normal/expected for the PATCH to PayPal to only include a breakdown for the default currency?
2. What would cause the PATCH to include a breakdown for a foreign currency?
3. Where is that patch calculated and where does it get its data from? (So that I can try and track down why it send GBP with the wrong currency)

(We’re also seeing “Breakdown mismatch. Items and breakdown ditched.” notes on all foreign currency orders – both correctly and incorrectly charged ones – but that just appears to be a WooCommerce/PayPal issue with foreign currencies as it appears to happen on _all_ foreign currency transactions and _none_ of the GBP ones)