Ask A Question

Notifications

You’re not receiving notifications from this thread.

Stripe Connect setup with Pay gem

Cal Findeiss asked in Rails

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?

Reply

Marketplaces can be pretty confusing. I think this sounds right, but I can't remember if the users receiving payments will need to be a Merchant or not.

https://docs.stripe.com/connect/design-an-integration

Stripe now uses Payouts instead of Transfers, so we might need to update Pay a bit to help with that functionality. They're constantly changing things so it can be hard to keep up!

Reply

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!

Reply
Join the discussion
Create an account Log in

Want to stay up-to-date with Ruby on Rails?

Join 86,796+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.