#hactually
1 messages ยท Page 1 of 1 (latest)
๐ not sure I follow. Could you share more details about what you're trying to achieve? Any payment data collected using Stripe.js will only be received by Stripe
that's fine - we don't want to get in the way of capturing the PAN etc but we want to make sure the payment is liked to the requested Connected Account and allow styling to be injected for our integrator
ideally they'd request the fields from us via API or a GET request and we'd return an iframe that contains the stylised Stripe widget
No, this isn't possible. The integrator should be including Stripe.js scripts directly into their site, and rendering elements based on a publishable key and client secret returned from Stripe for example
gotcha - how would we be able to process the payments for them and link it to the correct Connected Account?
Can you share more context? When using Connect, you'll either create payments on your platform (for Destination charges and Separate charges & transfers) or create payments directly on the connected account (if you're using Standard Connect): https://stripe.com/docs/connect/charges#types
If you're working with direct charges, you'll use your platform keys but include the standard account's ID server side and client side: https://stripe.com/docs/connect/direct-charges#create-a-charge
Sure - so we're integrating with a 3rd party who'll be embedding our page, which in turn holds a Stripe widget effectively. We do all the custom funds routing, payouts etc via Stripe but we are keen to know what we should/shouldn't do when it comes to iframing etc
I'm assuming the 3rd party doesn't interact with Stripe directly, only your team does?
How is Connect involved?
that's right - we are just the platform. The 3rd party calls our APIs and we have the connected account setup in our backend for the 3rd parties, merchants.
Similar to how Shopify uses Stripe to route the funds and manage the connected accounts but the client pays on a Shopify (3rd party) page.
๐ Taking over this thread, catching up now
If Stripe.js is used to collect payment method details, it has taken care of the security for you. For Connect, you would then need to follow the charge types that @.roadrunner shared earlier with you
gotcha - so we can host the element and be iframed as long as we're using the Stripe.js widget appropriately? There's no specific advice?
That should be it. If you face any issue during integration, feel free to let us know