Cal Findeiss

Thanks @chris. I saw that as well, figured it might be just some wording associated with gem vs stripe, but good to know that in Pay they aren't the same thing. Ill continue to look into connected account or just standard account with Users so they can receive payouts.

Thanks again for everything!

I am setting up a payment pathway in my application to accept and pay other users within the platform, but there is an extra step to this. A User belongs to an Organization.
user belongs_to :organization
organization has_many: users

The payment process would go:
User > Organization > User

So I believe that the Parent Organization would need to be the only :merchant that I would be able to setup a payment and transfer though.

So I believe it would flow something like, if the app was rideshare type:

1. User A marks ride as complete.
2. User B confirms and submits payment to Parent Org (merchant in pay and "connected account" in stripe)
3. Automatically Transfer from Parent Org to User A once the transfer's funds are available (this generally following this part of the documentation, https://github.com/pay-rails/pay/blob/main/docs/marketplaces/stripe_connect.md#separate-charges-and-transfers)

Am I missing something in the Pay gem flow or setup?