#CalebR - Connect webhooks
1 messages · Page 1 of 1 (latest)
Hello
Hello 👋 Stepping in here
Just to make sure I'm on the same page as you are (feel free to correct me if not)
You have a new Platform account where you've been onboarding new customers
when you say customers, does it mean new connected accounts or new customer objects?
Oh, sorry—new connected accounts
The account we received the dispute webhooks for was not an account that we have onboarded, and the disputed transaction was not processed through our connect integration
So I'm trying to determine why we received the webhook
Gotcha. Thanks.
- So you are onboarding connected accounts to a new platform account.
- When the connected accounts that are still using your old integration connect to the new platform account, you start receiving webhook events from these accounts that still links to your previous integration?
No, we have not onboarded them at all.
But are receiving webhooks for disputed charges
OH! Interesting...
Can you share your new Platform account ID as well as the old platform account ID ?
Our platform account is acct_0JMW53soKKKIrdr2RkEc
The old integration actually doesn't use Connect at all
We are connecting to Stripe as a gateway through Spreedly in the old integration
can you share the event IDs for the webhook events?
The account we received the webhook for was acct_1DoGjjESRuzkqMtU
One moment
Event: evt_3L69YGESRuzkqMtU0pY0ZHEj
This account does interact with us as a customer paying us through Stripe as well
Seems like the account is connected to your new platform?
You're saying you didn't onboard them?
sorry, I missed your message above where you confirmed you didn't.
There might be some confusion around what "onboarded" means
They are paying us through Stripe for our SaaS service, which I think is why they show up as a Connected account, but they are not processing any payments from their donors (customers) through Connect—all transactions between them and their end users are currently through Spreedly
Does that clarify things? Sorry it's a bit complicated.
Ah NP! I see.
You may want to refer to following
https://stripe.com/docs/connect/oauth-reference#:~:text=As a platform,Standard Platforms.
This is expected behavior I think
Hmm, okay. Is there any way for us to only receive webhooks if the charge originated with our Connect integration?
thinking...
If it helps, this is the legacy connection we're using: https://www.spreedly.com/gateways/stripe
Stripe is supported via Spreedly's unviersal payments API
Though we connect with more than just Stripe through Spreedly.
Yeah I'm not completely sure as there are more platforms involved here
There's this https://stripe.com/docs/connect/oauth-changes-for-standard-platforms
However, I'd recommend that you talk to our support team to get a more specific directions on this
https://support.stripe.com/?contact=true
Okay, thanks. I'll reach out to them.