#llh_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1267882058588487733
đ 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.
- llh_api, 6 days ago, 7 messages
context is I wanna use PaymentIntent API bc I wanna set dynamic MCC as well
Hello
Charges API has been considered legacy.. You should use putExtraParams
perfect tks for confirming, I'll give that a try. Do you know if stripe SDK would be updated to handle those edge cases?
I am not aware of such plans, no
we currently use charge api for some old bank account payment method token src_
can we switch to PaymentIntent API for those as well?
For bank account sources I'd recommend following the guidance here: https://docs.stripe.com/payments/payment-methods/transitioning#compatibility-reusable
Those are not compatible with PaymentMethods API directly