Stripe Connect changes?

[cwise]

Specifically, is anyone working on the changes to support Stripe Connect and payments with managed accounts.

This would be the following fields:

• destination
• application_fee

If no one is already working on it, I can do so. destination is a straight-forward change because it's effectively just payment_method preference additions. If anyone has a good idea on how to pass the application_fee through to the gateway, that'd be appreciated. That fee is essentially a holdback amount on the total when you are attributing an order to a sub account (destination).

[JDutil]

Not that I'm aware of you'll have to dig in on that.

[paololim]

@cwise - I am a little new to Spree, but need to figure out how to add a destination for a Stripe Connect implementation. This github issue came up in a Google search. Would you be able to detail a little more about what you might do?

[cwise]

Added preferred_destination to each Spree::PaymentMethod you add. If you go in to Spree::Admin you'll see this field available for entry if you edit a payment method. We populate login with the master API key and the destination with the connected account id.

[nghiapdx]

@paololim please share if you were able to get a working implementation of Stripe Connect Gateway.

[wjrobinson11]

And how do you add application_fee?

[giugrilli]

News on this?