#TomHS

1 messages · Page 1 of 1 (latest)

somber carbonBOT
real timber
#

by passing a source_transaction and a transfer_group, we probably update the Charge to now be associated with that group

#

I assume something else is broken and it doesn't generate a charge.updated event for that change in this specific circumstance , which is why you only see the change when looking at the next event which happened to be updating the description

fathom salmon
#

So if we are doing multiple transfers for the same payment, we'll have to reget the Charge and check that it hasn't got the transfer_group set?

real timber
#

sure

fathom salmon
#

Our logic currently is that we receive the webhook for a payment then initiate the transfers. I assume this one alone failed simply because there was a bit of a gap between the requests to create the first and second Transfers, and during that time Stripe updated the Charge with the first Transfer's transfer_group. Does that sound accurate?

real timber
#

well I don't understand why your logic would be trying to create two transfer with the two different IDs

fathom salmon
#

Christ I didn't realise they were different

real timber
#

yeah they are, the prefix starts the same so that is hard to spot

#

ultimately you don't even need this

#

we create the group automatically when using source_transaction so you don't need to pass it at any point

fathom salmon
#

I'm fairly sure there was a good reason we added it but I'm drawing a blank at the moment; I'll look into that. My issue is clearer now that I know the groups are different. Thanks.