#Kacper_Banasik-transfers

1 messages ยท Page 1 of 1 (latest)

silk pier
#

Hey!

stiff wadi
#

sure just a second

#

will id of the event be ok?

#

bc i can't find id of request

#

just to add we are working on test env

#

evt_1LeaRIJSpHh6jgs5dD3PmGMi

#

nvm got it

#

req_bSnGFwk2y6GeqK

silk pier
#

Taking a look

#

Seems like you're not using the source_transaction value you're expecting

#

And creating a new Transfer that references a py_xxx that has already been used

stiff wadi
#

so I'm getting charge id from wrong payment intent?

#

because i do:

silk pier
stiff wadi
#

checkout_session.payment_intent.charges.data[0].id

silk pier
#

This event evt_1LeaRIJSpHh6jgs5dD3PmGMi?

stiff wadi
#

yea

silk pier
#

I assume you're looking up the Checkout Session object and expanding the payment_intent field separately

stiff wadi
#

correct

#

stripe.PaymentIntent.retrieve(session.get('payment_intent'))

#

session = event['data']['object']

glad fern
#

Hey! Taking over for my colleague. Let me catch up.

stiff wadi
#

sure take your time ๐Ÿ™‚

glad fern
#

While analyzing this event evt_1LeaRIJSpHh6jgs5dD3PmGMi I see that Stripe did 3 attempts to deliver it.
The first one, your endpoint responded with 500 => here it looks like you created the transfer, but your server responded with 500 for another exception
The second one, your endpoint responded with 500 also
The third try, your endpoint responded with 400
You can see in your dashboard, the response that your endpoint responded (Analyze the event sent at Sep 5, 10:13 AM)
https://dashboard.stripe.com/test/events/evt_1LeaRIJSpHh6jgs5dD3PmGMi

stiff wadi
#

okay I will try to fix it according to dashboard events. Please do not close this thread so I can come back if we get any other errors regarding this case

#

anyway thanks for your help ๐Ÿ™‚