#lyncor
1 messages · Page 1 of 1 (latest)
Hi there, yes you can't change the transfer_group once it's set. So your system should generate a unique value for transfer_group and set it when you create a Checkout session (https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-transfer_group)
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yes, that's what I'm trying to do. However, I have two different steps in the system that need to be able to generate the same transfer_group based on the same input data.
I was hoping to include the session_id as that'll be unique for each checkout process, and I haven't seen any other bits of data that will be similarly unique.
If I add something like the current timestamp, the second step won't be able to re-generate the same transfer_group and use it to build the transfer to our merchant after the checkout succeeds.
The checkout session ID is only available after creation. So you can't use the checkout session ID for transfer_group
... 🤔 I suppose that the second step could read the transfer_group from the checkout's payment intent after fetching it, rather than idempotently generating it a second time.