-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add Stripe Connect support #117
Comments
So it looks like I can partially use #113 because now the subdomain will depend on the request. It's not exactly clear how subdomains for a request should interact with a configured subdomain. |
maybe configured hosts just flatly overwrite request hosts in all cases is ok |
Hey @aviaviavi , Apologies for the delayed response. This sounds awesome. As you've noticed Otherwise, the architecture is pretty straight forward. There are some fancy types (associated type families) to create an association between the stripe url-form-encoded parameters to the response JSON. Should be simple enough to define types and instances @aviaviavi, you can find inspiration from the previous Would love to upstream these changes into |
Hi @dmjio,
I'm interested in adding in functionality for a few connect endpoints. Currently, I'd like to be able to get connect's oauth tokens (https://connect.stripe.com/oauth/token) and managing checkout sessions (https://api.stripe.com/v1/checkout/sessions) and charging them. Might need some others as I go. I'm new to stripe so not sure how complex this is. Any help getting started would be appreciated!
The text was updated successfully, but these errors were encountered: