topfra

Addendum: The problem seems to be related to the browser cache (Edge). After clearing the browser cache, everything works again without any problems.

I’ll leave this post up in case anyone has a similar problem.

Issue is solved: https://github.com/woocommerce/woocommerce-gateway-stripe/pull/3243

I’m glad to hear that. So I’m not going to touch anything myself with Stripe, as they also offer a migration tool that transfers existing SEPA-payments to the new API.

Better if the plugin takes care of it.

BTW: Is there any release date regarding the “new checkout experience”-issue with SEPA? I have checked the newest release and the issue seems not to be solved yet, unfortunatley

Thanks

• This reply was modified 6 months ago by topfra.

Same over here. (ERROR Payment failed. No payment tokens found for customer XXXXX).

We use Woo Subscriptions in conjunction with Cartflows (paypal reference transactions enabled). For customers who do not yet have an account, an account is created when the order is placed. Like Ingo, I assume that the token cannot be assigned to a customer, as the customer account is only created later (when the attempt is made to assign the token to a customer).

The paypal tokens are also not stored in the “woocommerce_payment_tokens” table. In contrast to Stripe. On the (test) customer’s side, however, the payment agreement with the merchant (us) is stored in the PayPal account. Nevertheless, the corresponding PayPal account will not be debited when a renewal is attempted. Therefore, it really seems to be due to the fact that PayPal Payments cannot assign the “Token” to a customer id.

Is there an exact timing, as the entire payment solution is absolutely useless for us.