dev-in-need_docs

[earnest cairn]

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.

• dev-in-need_docs, 12 hours ago, 9 messages
• dev-in-need_docs, 13 hours ago, 24 messages
• dev_payout-funds, 4 days ago, 8 messages
• dev_connect-issuingmore, 5 days ago, 20 messages
• dev_connect-issuing, 6 days ago, 12 messages
• dev-in-need_docs, 6 days ago, 28 messages
  and 1 more

[serene geode]

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

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

[hollow mesa]

That event would fire whenever you make a call to update it: https://docs.stripe.com/api/issuing/transactions/update

Or whenever an attribute on the object changes: https://docs.stripe.com/api/issuing/transactions/object

[tall chasm]

could you explain when that would occur - from stripes end? Or would it only occur if I explicitly update the transaction

[hollow mesa]

As far as I know, if a Dispute is created, the transactions is updated. Basically, just read through the the different attributes on the object and let me know if you have any questions about any specific ones

[tall chasm]

ok sorry I am working through the webhooks to ingest the different authorizations, disputes, and transactions and trying to understand when or why I need to listen to the transaction updated event

but a refund or a credit will be a new transaction object - regardless of if its linked to an original transaction - right?

and if the original transaction is linked to a refund what changes on the original transaction?

[hollow mesa]

Correct

[hollow mesa]

The type attribute on the Transaction object

[tall chasm]

oh so the original transaction object becomes refund - even though a new transaction object is created of type refund?

[hollow mesa]

No, a new Transaction object is created with type: 'refund'

[tall chasm]

ok sorry but you said the type will also change on the original transaction ?

[hollow mesa]

No. Sorry, maybe I didn't explain that properly. The type will always be the same. If a Transaction with type: 'capture' gets refunded, then a new Transaction object will be created with type: 'refund'

[tall chasm]

ok perfect

thank you

I am just confused what gets updated on the original transaction object and why I would need to listen to transaction updated events.

[hollow mesa]

My recommendation is to listen to them and cache their contents as you continue testing different workflows. It will become apparent later on what you might want to use that webhook event for