#discodanne_api
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/1354145910870769705
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi! just to clarify, are you listening to thecharge.updated event? and your server didn't know how to handle this event because payment_intent is null?
We fetch charges on a schedule.
Yeah we trow an internal error since we lack the payment intent.
Nothing in this charge make any sense to me. We dont have any customer details, the We dont have a payment intent and the payment payment_method_details is of type stripe_account
I have always viewed the payment intent id as the main id since its the one you show in Stripe Dashboard
this charge is associated with a transfer - it originated with a call to POST /v1/transfers via the python SDK
https://dashboard.stripe.com/logs/req_Qpc2LnnbeGxRYa
so yeah, it's a little confusing that they both feed through to the same webhook endpoint, but this is a known scenario since transfers can also result in charges
We dont use the webhooks, we just fetch them from charges.
I only have Api key access and dont have acces to their dashboard. I cant see any transfers with the apikey
gotcha. yeah, the result would be the same whether you're retrieving them or getting them from a webhook. but the short version is that charges missing a payment intent is a known possibility in several cases - see our docs which call it out as a nullable string
https://docs.stripe.com/api/charges/object#charge_object-payment_intent
Yeah, but whats the cases its null?
And is it a charge or a transfer?
Or have they recieved a transfer from another account and that is why it does not show up propperly?
i already mentioned one, which is when you create a transfer - specifically one with a destination stripe account. these result in a destination_payment, and that payment also counts as a charge for API purposes
https://docs.stripe.com/api/transfers/object#transfer_object-destination_payment
the platform account acct_15bvVXIDkGDhAX2x created a transfer to acct_1LKnTwEK2Tuo9Sfz which resulted in this transfer + charge
Okey thanks.