splitrox_webhooks

[serene fulcrum]

👋 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/1313470803991466048

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[tidal stag]

It depends on what information you need, but yes payment_intent.succeeded could suffice

[last gorge]

I would probably say Payment Session would be important, when someone goes to the checkout a payment session is created which contains the token (cs_test_....) In order for me to properly update this payment session I need to get this id i assume which i can't get via payment_intent_succeeded? (without an extra HTTP request)

Or if there is any other information i can have access on the checkout creation and payment_intent.suceeded so i can connect both data

[tidal stag]

I need to get this id i assume which i can't get via payment_intent_succeeded?
Correct. you can't get it from that event

If you need to get data from the Checkout Session, then you need to listen to the other events then.

[last gorge]

Which I assume are checkout.session.completed, checkout.session.async_payment_succeeded correct?

[tidal stag]

Correct yes

[last gorge]

Also another question i have is regarding the refunds. There are some events regarding refunds but i'm not sure which one i should use. what are the ones i should use to know when someone opened a refund, when they lost the refund or when they won the refund?

[errant token]

hi! I'm taking over this thread.

you can listen to refund.created and refund.updated

[last gorge]

Sorry, can't seem to find that event, the most similar i can find is charge.refund.updated and charge.refunded

This is with stripe test environment (stripe trigger --help)

[errant token]

these are new events, so might not be supported by stripe triggers.

but if you trigger charge.refund.updated or charge.refunded, I think you should also receive the new events

[last gorge]

Let me try!

Oh yeah, i got a refund.created and a refund.updated, let me take a deeper look to see if i have further questions, thank you!

So I was checking refund updated and I have some questions.
On my system I have 2 objects. PaymentSession (to proceed to checkout and lifecycle ends when payment completed) and PaymentTransaction which is the actual payment. Currently I'm storing the Charge only and not the payment intend, is this an issue? Because I assume a payment intent might have multiple charges for example if a payment intend gets a refund stripe applies a fee I assume?

Also i see a data.status which is succeeded, is succeeded as the customer won the dispute or succeeded as myself won the dispute?

[errant token]

Currently I'm storing the Charge only and not the payment intend, is this an issue?
a PaymentIntent can have multiple charges, especially if a charge fails. so in general I would recommend to store the PaymentIntent rather than the Charge.

[last gorge]

If I remember in the past i was using charge because if used payment intent i had to do more http requests to fetch more information but I'll take a look, thank you

[errant token]

A dispute with status won is won from the point of view of the merchant, which means the customer lost the dispute

[last gorge]

I can see on the refunds object which i assume is the response several options:
"pending, requires_action, succeeded, failed, or canceled"
In this case as I only want to know if i won or if i lost i assume is succeeded and failed?

I'm not really sure about the status when i lose the refund

[errant token]

In this case as I only want to know if i won or if i lost
I'm confused. are you talking about Disputes (which can be win/lost) or Refunds (which are succeeded/failed)?

[last gorge]

Apologize, probably I mean dispute? I assume refund is specifically when someone really indeed gets a refund

In that case what events should i listen to? In order to know when someone opens a dispute, wins/loses a dispute

[errant token]

got it. for Disputes, you can find all evenst here: https://docs.stripe.com/api/events/types#event_types-charge.dispute.closed

and I recommend reading this guide: https://docs.stripe.com/disputes

[last gorge]

Thank you very much. I can see several status, are final status only won and lost or a dispute can end with another status? I can see there is the "warning_closed" but I don't understand if I have to worry about this at all if i only want to know if they won and lost, at least i need to know when the dispute is really over.

[errant token]

The status warning_closed means the issuer did not escalate the inquiry within 120 days, so you can treat is as won this is explained here: https://docs.stripe.com/disputes/how-disputes-work?dashboard-or-api=api#inquiries

I can see several status, are final status only won and lost or a dispute can end with another status?
not sure which status are final, but you should definitely listen to charge.dispute.updated to be notified of status changes

[last gorge]

Oh so from what I understand, the dispute could be even created even before a refund request (chargeback) initiates?

[errant token]

not sure, we don't know much about how disputes work on Discord. but if you have more questions about this, you could ask Stripe support: https://support.stripe.com/contact

[last gorge]

Apologize for the extensive questions. Thank you anyway tho

[errant token]

happy to help 🙂

[last gorge]

Hey, one more question about the triggers. Do you have any idea how i can fire charge.dispute.closed or charge.dispute.updated because on stripe console i'm getting:

When i do stripe trigger on my own computer i can see charge.dispute.updated and charge.dispute.closed on my trigger list but from Stripe CLI i can't see them there

[errant token]

you mean when you try using the Stripe CLI from the Stripe dashboard you don't get all the events?

It's possible the version we use on the Dashboard is not up-to-date

so you have to use the Stripe CLI on your own computer. or directly use the Stripe API.

[last gorge]

I'm confused 😅 How can I use the Stripe CLI from my own computer? on your docs i can only find the stripe login, not the cli

[errant token]

earlier you said:

When i do stripe trigger on my own computer
and now you are asking
How can I use the Stripe CLI from my own computer?
so I'm confused. do you have the Stripe CLI installed on your computer?

[last gorge]

I'm so sorry, I'm the one confused, i was looking for a stripe cli on my computer but i can just do stripe trigger <name of the trigger>