#Champian

1 messages · Page 1 of 1 (latest)

open sedgeBOT
dense coral
#

Hi there!

#

Can you share a request ID (req_xxx) where you see that error?

spare lotus
#

sure

#

req_2Qmn8mYISZT6NL

open sedgeBOT
unkempt eagle
#

Thank you, checking in to that request

#

Ah, so it looks like you have a PaymentMethod saved to that Customer rather than a Source, unfortunately default_payment_method doesn't work for one-off payments the same way that default_source did

#

So you can make this call but you need to explicitly use the PaymentMethod's ID when making it

spare lotus
#

is this due to a recent change?

#

I'm not familiar with how my customers add their cards since I havent had to be, but this problem has also cropped up very recently

unkempt eagle
#

Not a recent change on Stripe's side. PaymentMethods and Sources have always worked like this as far as I am aware. Though it sounds like this may have been a change in your system for how you save these cards to your users

spare lotus
#

yes it may be, we use WooCommerce

#

ok thank you I will investigate!

unkempt eagle
#

If your company is writing your own server-side code here my guess is that you moved to saving cards with SetupIntents which create PaymentMethods like the new one that you have saved to this customer (pm_1NExDpJGKyBM9DgMCxSKXtW5)

#

Ah gotcha

#

So yeah you may need to change your code hten if you are the one making these calls to create the Charges

spare lotus
#

I may just list out their payment methods and have the user save a default one on my own interface to it all

#

I am

#

thank you

unkempt eagle
#

Yes

#

Actually now that I type that out, I realize that you will need to make a slightly different call. Charges don't support our PaymentMethods API, so you will want to charge users with your PaymentIntents API instead

#

One sec finding the doc that demonstrates this