nanorepublica_webhooks

[uneven charm]

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

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

[prisma nimbus]

Hey there, looking into this

So looking at the first event evt_1SpUOZC3XbGFWaf89AFKkUtj i can see this is type=capture so the payment is already fully complete, and isnt updated later

In general, updated events would only happen when there is some later change to an object

Do you have any examples with different behaviour?

This seems to align with our docs indicating that a transaction is only created with the authorization is approved and captured
https://docs.stripe.com/issuing/purchases/transactions

It is possible this only happen if you update metadata, for example.
https://docs.stripe.com/api/issuing/transactions/update

Is there something else that suggests other reasons you are expecting the updated event?

[astral inlet]

Thanks for looking into this. It was this in the dashboard that made me think that 2 events might be fired for created and then posted. This also seems to be the case for events I am dealing with (Transfers/Payments from Treasury)

I think you have confirmed this, but to double check. I should consider a issuing_transaction.created money leaving an account via a card (a posted transaction) and the pending of this can be linked to the authorization being created?

[prisma nimbus]

I don't know Treasury deeply, but I think that "posted" detail is related to the treasury account debit, somewhat disconnected from the issuing transaction (even though they are related)

All the posted events are under the Financial Accounts section here: https://docs.stripe.com/financial-accounts/connect/examples/webhooks#financial-accounts-for-platforms-webhook-events

[astral inlet]

I'm aware of those and do get they are different products.

Thanks for the clarification, I will change my app to treat authorizations as pending and transactions as posted

[prisma nimbus]

I can't really speak to the "posted" part as i said, sicne that gets into treasury territory.

But the flow and vsarious states for the authorizatin and transaction are described here: https://docs.stripe.com/issuing/purchases/authorizations#authorization-updates

[prisma nimbus]

As far as i am aware, there is no concept of "posted" strictly within the scope of Issuing (before considering Treasury for funding).

There is an authorization that you approve or decline, it can later be partially or full captured, or expired

When captured, it produces an issuing transaction

[astral inlet]

It is that screenshot of the Dashboard that has me confused, where the "Transaction created" then "Transaction posted" immediately afterwards

[lunar yew]

Hi taking over here as synthrider has to step away. For reference, we don't really know anything about the dashboard in here so can't speak to those statuses it shows. Also we know limited things about Treasury and Issuing unfortunately so I do recommend you reach out to Stripe support for help on this: https://support.stripe.com/contact

[astral inlet]

Ok thanks! It's the comparison of the API and what's happening in the Dashboard that has me confused as I assume the API drives the Dashboard in this case?