#claudiuyoro_webhooks
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/1435164976448012298
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there ๐ give me a moment to catch up
Hi! Sure, take your time
Hey!
Just to confirm, you want to change the PaymentIntent's Description from "Subscription Update" to something else? For example, pi_3SM5RfGJ9Vvm2nnN0ALNziit current description is Subscription update
Yes,that's right.
@obsidian quartz looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
Yeah, its not possible to change it at the PaymentIntent creation stage, because the PaymentIntent was automatically created from a Subscription. The workaround is to retrieve the created PaymentIntent and update the description, after the subscription has already created the PaymentIntent.
ok and If I change the description when I create the subscription, is that going to affect this or not?
Also, that's the only workaround? I have a different platform (Oblio) that I integrated with Stripe and automatically reads that description. I am not sure, but there might be issues with it like it reads first the "Subscription udpdate" and I update it later which is not going to be useful for my use case.
Changing the description on the subscription during subscription creation wouldn't affect the "Subscription update" description on the created payment intent when the subscription cycles.
Updating the PaymentIntent's description after the payment has been created is the only workaround if you need a different description on the PaymentIntent
I'm unfamiliar with how other third-party platform works, but would it be possible to read the product data from the Subscription's Invoice instead of the PaymentIntent?
Unfortunately not, the other platform is more of like plug and play.
so, how would that be best to do it?
I guess i am not going to do it through a webhook, because there is high risk.
I just read something now about this:
expand: ["latest_invoice.payment_intent"], --> when creating a new subscription. Is this going to work?
Like I extend i, then I update the payment intent.
But, again, I am not sure if it's going to work for future payments as well.
So, basically the only solution from my understanding now would be to "read the product data from the Subscription's Invoice instead of the PaymentIntent" ?
Because the webhook trigger I am not sure if it's a safe solution.
I am abit confused, why would it not be a safe solution?
Retrieving product data belonging to a subscription is usually done either from the Subscripton directly, or from the Invoice's Line Item, because these are Stripe objects that carries the product data. PaymentIntents do not carry product data from a subscription
What you mentioned makes sense, but probably I have to handle with the other party to check if they can offer this.
Right now, they read from PaymentIntent from what I have seen.
Anyway, it's a lot more clear now and I will discuss with them to see if they could do it this way.
Thanks a lot for the information!
No problem!