#netbar93_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/1467961869187940453
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
HI 👋
You should always be using Payment Intents. Direct Charges integrations are deprecated
How are you creating these payments?
Hey Hey!
So if I’m a Stripe app, my users create their own pages, and I want to implement the Stripe app that will customize the bank statement to what is relevant to the order
What do you mean "my user creates their own pages"?
At what point does your Stripe App interact with the Payment Intent?
It might be possible to listen for the payment_intent.created webhook event and then Update the Payment Intent with the statement_descriptor_suffix parameter
and payment_intent.created create every new enter to any checkout page?
and for '"my user creates their own pages"' i meant for checkout pages so of them have API checkout and some not
At what point does your Stripe App interact with the Payment Intent?
my app installed once and from then on it's lisen to the payment_intent.created see the order and then update the bank statement
and payment_intent.created create every new enter to any checkout page?
Ah no. If they are using Checkout Sessions the Payment Intent is not created until the confirmation process
And most of the Stripe users work with checkout sessions, right?
There is no way that I load the pre-order and may have a data just for the code as a db gallary to pull and update the statement?
Hello
Jumping in as Snufkin needs to step away
I'm not sure what you mean by
And most of the Stripe users work with checkout sessions, right?
There is no way that I load the pre-order and may have a data just for the code as a db gallary to pull and update the statement?
Can you elaborate?
I will try to explain in detail the business idea, and I need to understand whether it is possible to implement it.
We are building an application called Dynamic Descriptor Optimizer.
What it does is basically solve the problem that customers do not recognize where the bill came from, and there is a generic name of a company that most likely does not remember or have even seen its name on the site.
I want when I receive some kind of webhook or any event of a user going to an OpenAI-style checkout page and the like - they all seem to be the same thing that is used in your interface - there I want to burn the data of the updated bank statement to it.
Or at any other stage, but yes, to insert the updated bank statement to it, and it will also be in the result.
serve as stripe app that you install and set setting in the onboading and from now on it's running on any transction
When you say, OpenAI style checkout page - do you have an example screenshot?
yes i mean to the payment link style
Gotcha. Payment links create a Checkout Session under the hood. As Snufkin explained, the PaymentIntent isn't created until the Checkout Session gets confirmed. So you won't be able to set the descriptor by listening to a webhook event.
Are these recurring charges (Subscriptions) or one-time payments?
this one is for one time in the sandbox
there is any way we can do this app? you would want to build something like it ? before i giving up and moving to the next idea
it can solve a huge problem
and everyone is losing the disputes to confusion beacuse of it
I can't give any opinions on this myself but for one-time payments, you can set the descriptor suffix while creating the Checkout Session using the API (rather than using Payment Links) - https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-statement_descriptor_suffix
Setting a suffix there would set it on the PaymentIntent when it gets created
but stripe user can install my app and it's will be apply to their one-time payment?
If you create the Checkout Sessions on their behalf, yes. If you're thinking about webhook based async approach then most likely the answer is no
ok and i need to create the all checkout session or i can just update it?
You can't update it once it's been created. Update API only supports - https://docs.stripe.com/api/checkout/sessions/update
OK, what I try to understand - this will be covered for whom? Which users will not be affected ? For sure, if you agree with the app.
I think your question is a bit vague and lacks context. When you say "covered for whom? Which users will ...? ", what does that mean exactly? 😅
I’ll try to explain myself better. 🙂
There are many ways people use Stripe. Some use the API, some have a payment link, and some use the checkout session.
Now, I want to understand which group of users my stripe app will work for if I update the checkout session. Who will it update, and who won’t?
A lot of usecases rely on creating the PaymentIntent directly and don't use Checkout Sessions API at all. So your potential integration would only solve it for fractional of Stripe users that rely on Checkout Sessions API.
Got it thanks appreciate your help!
And as we said before I'm just making sure again I can't work with the PaymentIntent creation directly and update? Not even in advance?
I'm not sure if you can do that with a Stripe App. You could do it with a Connect Platform but that will increase the complexity of the integration.
can you share with me relevant docs?
Yeah but the integration complexity is quite high
there isn't a single solution that'd fit all Stripe user's usecases.
You'd need to study each API Stripe users integrate with, how you can "plugin" and handle it with as less integration challenges as you can
would require a lot of testing to see if you run into any API limitations
but you beacuse it's "just" the update so the flow will be the the user sign up with stripe to my web app and then it's been "plug-in"?
Hi, jumping here, I'm working with @manic lichen . can we listen to the webhook payment_intent.created and update the PaymentIntentParams.StatementDescriptorSuffix?
do we get enough time to update it before it's status change that will lock the update?
do we get enough time to update it before it's status change that will lock the update?
It depends. if the integration is doing client-side confirmation then you may have time.. If they're doing server-side confirmation with existing/pre-saved payment methods (by passingconfirm: trueparameter) then you probably won't