#RoyalPeasantry - transfers
eternal ice
Transfer groups are usually used to track transfers that relate to specific charges (in a Connect scenario).
But that does not preclude you for using the transfer group in this manner. You would just need to watch out for duplicate string values
eternal ice
Okay. The intent is to link multiple transfers as part of a group by a shared transfer_group string value. So we don't enforce any kind of uniqueness
pearl phoenix
yeah well - I need some way to prevent a transfer from being created if it was already created..
that doesn't seem to really exist
eternal ice
That would be something your integration would need to handle.
pearl phoenix
I'm very suprised stripe doesn't have support for this
and I would handle it in my integration, but it isn't actually possible
I have no guaranteed way to figure out if a transfer succeeded or not if the request times out.
eternal ice
Well if you are using Stripe client libraries and idempotent requests you should be fine to retry the timed out request.
pearl phoenix
That helps - but I don't think the client is really designed to make that work across processes
plus it says that it will also cache a 500
which is incredibly inconvenient
It also doesn't work if the retry is more than 24 hours later
which is really not unlikely in an error case
hmm - looks like I can actually pass my own idempotency key in fairly easily
which helps
though the server caching 500s is frustrating
and still doesn't solve the 'its been more than 24 hours' problem
floral stump
Hi, stepping in as snufkin needs to step away. Let me catch up here