#Scott

1 messages · Page 1 of 1 (latest)

mystic cedarBOT
lusty rivet
#

Thank you for the help 🙂

past lark
#

users that are somehow not having their form submitted, after their payment was approved

#

I don't understand what this means. Are you talking about some other form? How are you triggering this?

#

but this would entail each and every one of our users installing a webhook into their account
Not so! As a platform, you can configure a single Connect type webhook endpoint to receive the relevant events for all connected accounts

lusty rivet
lusty rivet
#

Can this Connect framework be used with only a set of API Keys? Or will I need to be added onto every client's account as a team member?

past lark
#

I'm not sure what you mean, but none of the API interactions require team member setup

#

This requires the client accounts to be connected to your platform account. Is that the case here?

#

Sorry, I assumed from the description you were using Connect, but I should have asked.

lusty rivet
#

No worries - we don't use Connect yet. How does one connect an account to another account? And are there any barriers to becoming a platform account?

We currently use the payment intent API via our clients' pk & sk keys.

past lark
#

Got it -- yea if you're performing actions for many other accounts, Connect is strongly recommended instead of handling keys

#

and the connect overview

lusty rivet
#

I've read through this, and i just want to confirm: this will maintain my existing process without any changes, and just send through the webhook in addition, correct?

#

Thank you so much for your help on this, by the way, i would have never thought of this myself.

past lark
#

Using direct charges (you authenticate "as" the connected account on the API request), the payment still belongs to the connect account, just as it does right now

#

You gain the option of charging a platform fee and you get the webhooks etc

lusty rivet
#

Gotcha - I will read through this. Thank you!