#maxim-k_api
warm wrenBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1328559396795584623
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- maxim-k_api, 5 hours ago, 46 messages
- maxim-k_api, 7 hours ago, 31 messages
- maxim-k_payment-element-usbank, 4 days ago, 46 messages
- maxim-k_api, 4 days ago, 34 messages
- maxim-k_api, 5 days ago, 62 messages
steel carbon
Hello
cursive walrus
hello! how can I help?
steel carbon
In order to replace outdated Source API, i'm doing a call
stripe.PaymentMethod.modify(
"ba_1Qh0AXAZsVWZrzM8PJ3SJlmx",
billing_details={
"address": {
"city": metadata["billing_city"],
"country": metadata["billing_country"],
"line1": metadata["billing_address"],
"postal_code": metadata["billing_zip"],
"state": metadata["billing_state"],
},
},
)
see req_Do0uYwAJMuGV6j
cursive walrus
i'm not sure I understand what you're trying to do specifically, ba_ objects are different from src_ objects. Why do you need to modify this object?
steel carbon
I noticed ba_* and card_* should be back compatable with PaymentIntent
cursive walrus
yes, it is backwards compatible
cursive walrus
no, that's incorrect. There is a Source object ( with the prefix src_) which is what's being deprecated (except for cards). There's a BankAccount object (with the prefix ba_) which is not deprecated, and there's a Card object (with the prefix card_) which is also not deprecated.
steel carbon
but after January 31 Charge() API will no longer available?
to charge ba_ and card_
?
cursive walrus
did the notice say that? afaik the notice itself didn't say anything about Charge API not being available
steel carbon
So, we can follow use customer.modify_source and Charge API after January 31?
cursive walrus
do you have an example request id for customer.modify_source which I can take a look at?
steel carbon
Also, fix me if i'm wrong. Can i use ba_* and card_* with PaymentIntent?
I don't have it handy
this something i've told 5 days agfo
Got it, thank you!
Last question
Is offline charging of old "src", "ba", "card_" payment sources. We can switch and PaymentIntent against them instead of Charge?
Pompey — 1/8/25, 3:58 PM
Yep, the PaymentMethods API is backwards compatible, so you can provide those IDs anywhere that our API is expecting a pm_ ID
that's why i'm asking, why stripe.PaymentMethod.modify() doesn't accept it?
So, it is important. Will Charge() API will be active for ba_ and card_ after Jan 31?
I'm confused
two methods: stripe.Customer.modify_source()
cursive walrus
the error message mentions that PaymentMethods of type us_bank_account cannot be updated at this time - this means that you can't update ba_ objects. I don't have context on why we don't allow modification of the ba_ object off the top of my head
steel carbon
and stripe.Charge.create()
cursive walrus
I've mentioned that ba_ and card_ objects are not deprecated, and the Charge API can still be used. If you want to be certain, you can always reach out to Stripe Support : https://support.stripe.com/contact