Open gerdneuman opened 4 years ago
I've seen something very similar again as part of #1145, but this time it is not a credit card => sepa, but sepa => sepa change:
With the next renewal payment this results in the error message being The source src_NEW is attached to a different customer than cus_OLD. Please charge the source using that attached customer.
as outlined in #1145:
Error: stdClass Object
(
[error] => stdClass Object
(
[message] => The source src_NEW is attached to a different customer than cus_OLD. Please charge the source using that attached customer.
[param] => source
[type] => invalid_request_error
)
)
After editing the subscription and changing the stripe customer ID to cus_NEW, and then creating new renewal order manually and processing the renewal payment of it, then the payment works.
Altogether it seems that adding or switching SEPA sources seems not very robust.
I'm tagging this issue with Priority: Low
, since so far it seems this issue has only been reported once.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
src_
is successfully registered at stripe.com for the existingcus_
(number 1 in screenshot)Stripe Source ID
at WooCommerce'sEdit subscription
page is correctly updated (number 2 in screenshot)Payment method
above theStripe Source ID
remains still to be set toCredit Card
(number 3 in screenshot)Expected behavior The subscriptions billing dropdown/select
Payment method
above theStripe Source ID
needs also to be updated toSEPA
(number 3 in screenshot)Screenshot
Environment (please complete the following information):
Additional context This happens from time to time in our shop, not sure if always or only in edge cases. If you need any infos from certain logs, either from WooCommerce's shop logs or from the stripe.com account logs, then let me know. I would try to dig into the logs and see if I could find what you need.