Confirm the behavior of SEPA Debit Sources used as a PaymentMethod about woocommerce-gateway-stripe

[namiokuzono]

For workaround on renewal subscription, please see 8056842-zd-a8c

Workaround: There has been report from merchants that switching back to Classic Checkout re-enables the SEPA payment.

[a-danae]

👋 Update over here.

Regarding subscriptions changing their payment method to Manual Renewal after disabling the Legacy checkout experience. I've tested the following snippet...

add_filter( 'woocommerce_subscription_get_payment_method', 'use_sepa_updated_checkout_gateway_id_for_subscriptions' );

/**
 * Filters the return value of 'WC_Subscription::get_payment_method()'.
 *
 * Returns 'stripe_sepa_debit' if UPE is enabled and the gateway is 'stripe_sepa'.
 *
 * @param string $value The payment method ID.
 * @return string
 */ 
function use_sepa_updated_checkout_gateway_id_for_subscriptions( $value ) {
	if ( 
		'stripe_sepa' === $value && 
		class_exists( 'WC_Stripe_Feature_Flags' ) && 
		WC_Stripe_Feature_Flags::is_upe_checkout_enabled() 
	) {
		return 'stripe_sepa_debit';
	}

	return $value;
}

... and things seem to work as expected:
✔️ Subscriptions display "SEPA Direct Debit" under "Payment Method", instead of "Manual Renewal".
✔️ Renewals are processed successfully when triggered by either the merchant or the subscriber.

This could be a workaround while we make adjustments for the upcoming releases. Please keep in mind this is a workaround and experimental, although tested. The actual fix will be released in the extension.

---

What's going on
I included the details of what's causing this behavior in the description of this draft PR, which exists as a proof of concept and to document the behavior, likely not getting merged.

---

The following flows fail when using a SEPA source with the Payment Methods API

• Regular purchase

There was an error processing the payment: Using a SEPA Debit Source in the payment_method field has been deprecated and is no longer a valid integration path. Please migrate your Source objects to PaymentMethods using the Dashboard migration tooling here: https://dashboard.stripe.com/sources-migration

• Purchasing a subscription

There was an error processing the payment: Using a SEPA Debit Source in the payment_method field has been deprecated and is no longer a valid integration path. Please migrate your Source objects to PaymentMethods using the Dashboard migration tooling here: https://dashboard.stripe.com/sources-migration

• Purchasing a subscription with a free trial

SEPA Debit Sources used as a PaymentMethod are not supported with the Setup Intents API. These Sources have mandate information and thus are already "set up"

• Changing the payment method of a subscription as a shopper

SEPA Debit Sources used as a PaymentMethod are not supported with the Setup Intents API. These Sources have mandate information and thus are already "set up".

✔️ Subscription renewals work as expected in my tests when using a SEPA source with the Payment Methods API.

---

I didn't get the message from the initial report when testing different flows, though. Consistent replication steps would be appreciated, but we'll continue checking these in the meantime.

SEPA Debit Sources used as a PaymentMethod have mandate information already stored. You cannot pass the mandate_data or mandate parameters. Please re-confirm without those parameters.

[a-danae]

We've created the following two issues for the reported behaviors:

• #3133

  • 8035522-zd-a8c
  • 8056842-zd-a8c
  • 8130440-zd-a8c
  • 8135622-zd-a8c
  • 8104366-zd-a8c / https://wordpress.org/support/topic/upe-sepa-not-working
  • https://wordpress.org/support/topic/no-sepa-payment-with-new-checkout-experience/

• #3134

  • 7886598-zd-a8c
  • 8119078-zd-a8c
  • 8090629-zd-a8c
  • 8130440-zd-a8c
  • 8115012-zd-a8c
  • 8049601-zd-a8c
  • 8168237-zd-a8c
  • https://wordpress.org/support/topic/using-a-sepa-debit-source-in-the-payment_method-field-has-been-deprecated/
  • https://wordpress.org/support/topic/no-sepa-payment-with-new-checkout-experience/

I'm closing this issue in favor of those two, which are more specific to the problems merchants are facing.

[mriyazuddin]

• #8035522-zd

[namiokuzono]

8056842-zd-a8c

This issue impacts merchants with subscriptions and its renewal payments.

Would like any insight on how one might workaround this issue. Is downgrading Stripe version the best way to handle?

[carolframen]

8104366-zen

[RiaanKnoetze]

From the forum post, a community member shared the following workaround:

---

Manually:

• You have to first go to the subscription, within the subscription, edit the billing information (pencil icon), search for the payment method and select the recorded SEPA mandate.
• Now you can change the payment method in the order related to the subscription, in the same way, edit the billing information (pencil icon). If you don’t subscribe first, it won’t leave you in the order.
• Change the status to pending payment and in order of actions you can try to collect the subscription again.

Bulk editing:

• I did the bulk editing with the WP Sheet Editor plugin, the payment method field is read-only by default, but it can be changed and modified with the right click. The process is the same as manual, first the subscriptions and then the generated orders.

[Mayisha]

8119078-zd-a8c

A similar issue has been reported here. After updating the Stripe plugin the merchant enabled the new checkout experience. Customers who had previously purchased from their store using SEPA are getting the following error and the same error is recorded in the order notes as well.

SEPA Debit Sources used as a PaymentMethod are not supported with the Setup Intents API. These Sources have mandate information and thus are already 'set up'.

The error message is different from the one in the description but the possible reproduction steps are the same. This started happening after enabling the new checkout experience and for customers who had used SEPA in the legacy experience prior to the update. Note that, the payment gets completed for this merchant when customer tries again (it is not clear from the discussion if the customer retired with the same saved SEPA payment token or a new SEPA token)

[shameemreza]

Another report here: 8104366-zen
Forum thread: https://wordpress.org/support/topic/upe-sepa-not-working/

There was an error processing the payment: Using a SEPA Debit Source in the payment_method field has been deprecated and is no longer a valid integration path. Please migrate your Source objects to PaymentMethods using the Dashboard migration tooling here https://dashboard.stripe.com/sources-migration

[hesne]

@RiaanKnoetze This will not help. I get the same error when changing it manually.

[namiokuzono]

8090629-zd-a8c

[carolframen]

8130440-zen

[sverleis]

8135622-zen

[Thelmachido]

8135622-zd-a8c

This issue impacts merchants with subscriptions and their renewal payments.

As @namiokuzono asked should we suggest a downgrade?

[OmarFPG]

Another one with:

Using a SEPA Debit Source in the payment_method field has been deprecated and is no longer a valid integration path. Please migrate your Source objects to PaymentMethods

I see other cases with this error message shared here. Are they related or should we open a separate GH issue?

8115012-zd

[shohanhossainnab]

8049601-zen

[shameemreza]

Possibly another report: 8168237-zen