-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow setting transfer_group
identifier
#33
Comments
Well, if I'd kept reading, I'd have learned that we might be able to retroactively group these, when creating Transfers in Stripe… I'll continue to investigate. ✌️ |
What's your timeline for this? |
Nothing urgent. Still in the proposal phase for the project, and doing some research! If we find ourselves at an impasse, I'm happy to issue a PR—I imagine this is a pretty infrequent use-case, and it may already be handled by the Transfer API. Will @ you if I find out anything actionable! 😄 |
The Sorry for the delayed notification :( |
We're looking at implementing a kind of merchant system for event ticket sales, and would love to have a way of sending an initial
transfer_group
param for Charges. Periodically, we're going to make Transfers to event organizers (carts may contain tickets from multiple organizers), and pairing these up will make record keeping much easier—and (in theory) tie them together in the Stripe dashboard.I appreciate the decision to ignore modifications to the
Transaction
object when emitting theEVENT_BUILD_GATEWAY_REQUEST
, but because this is a core param (and not ametadata
candidate), we don't have a way of including this.Is that something to be accomplished with a custom event? Probably not something to do by default, but emitting
EVENT_ASSIGN_TRANSFER_GROUP
would be super useful!…or, maybe there's another way to tap in to the request params, already?
❤️
The text was updated successfully, but these errors were encountered: