CalebR | Stripe Developers | Page 1

signal lindenBOT Apr 19, 2023, 12:56 PM

#

muted sable Apr 19, 2023, 12:57 PM

#

Most recent occurrence is du_1MsIpdESRuzkqMtUeHwtedgr

plush mortar Apr 19, 2023, 12:57 PM

#

Hello 👋
Are you a connect platform? And do you have a connect type webhook?
If so, that might explain why you're getting these events.

If you share an example event then I am happy to take a look

muted sable Apr 19, 2023, 12:57 PM

#

Yes, we're using Custom Connect

#

Let me see if I can find the event ID as well

plush mortar Apr 19, 2023, 1:01 PM

#

I found the event, looks like it was sent to the URL starting with https://demo.reachapp.co

#

That seems to be connect type webhook on your platform account

#

Where you are listening for dispute events

#

So this is all expected

muted sable Apr 19, 2023, 1:03 PM

#

Right, but when we attempt to retrieve the event data, we're not able to do so

plush mortar Apr 19, 2023, 1:05 PM

#

How exactly are you trying to retrieve the data?

muted sable Apr 19, 2023, 1:05 PM

#

dispute = Stripe::Dispute.retrieve({
  id: stripe_id,
  expand: ['payment_intent']
})

#

Where stripe_id is the du_ identifier we receive in the event

plush mortar Apr 19, 2023, 1:07 PM

#

You need to pass in the Stripe-Account header as the event belongs to the connected account
https://stripe.com/docs/connect/authentication

muted sable Apr 19, 2023, 1:08 PM

#

Okay. The other problem here is that this is not a platform account—they have a direct relationship with Stripe, and we are not managing their account through Connect

#

So we would like to be able to receive these notifications only for our Connected accounts.

plush mortar Apr 19, 2023, 1:09 PM

#

I'm confused. If you are not connected to the account then you shouldn't be receiving these events.
I think there's a misunderstanding here somewhere

muted sable Apr 19, 2023, 1:10 PM

#

That's why we are confused as well

#

This account shouldn't be connected to our platform account

#

We previously integrated our application with payment gateways (including Stripe) through Spreedly. Some of our customers are still using this legacy integration. When we started using Stripe Connect, these accounts somehow became connected to our platform account without going through the Connect onboarding flow

#

You can see this when looking at the account in question (acct_1DoGjjESRuzkqMtU)—there's nothing in the API logs for the platform section

plush mortar Apr 19, 2023, 1:28 PM

#

Ah I think I know what's happening here. We may have this documented somewhere..

plush mortar Apr 19, 2023, 1:43 PM

#

ugh can't find the doc.. still looking..

muted sable Apr 19, 2023, 1:44 PM

#

Thanks

plush mortar Apr 19, 2023, 1:57 PM

#

There's some information here
https://stripe.com/docs/connect/oauth-changes-for-standard-platforms

#

https://stripe.com/docs/connect/oauth-standard-accounts#:~:text=As a platform%2C remember that data you create for a Standard account (for example%2C charges%2C customers%2C invoices%2C and so on) will be visible on their Stripe account. It also means that if they connect other platforms%2C those platforms can access this data too.

muted sable Apr 19, 2023, 2:01 PM

#

I'm not sure that helps. We didn't use the OAuth flow mentioned there, and the Spreedly process doesn't have any connection to our platform account that I know of

plush mortar Apr 19, 2023, 2:03 PM

#

Ah hmm.. Let me pull in a colleague.

muted sable Apr 19, 2023, 2:05 PM

#

Thanks! Is there somewhere in our account logs I should look to see if there's information on how the connection was made?

plush mortar Apr 19, 2023, 2:06 PM

#

Okay so the reason you're seeing this event is because they are connected to your platform..
Looking into when this connection was made..

#

and how

muted sable Apr 19, 2023, 2:07 PM

#

We also use Stripe to collect payment from our customers, but that should be separate from Connect

#

For this account that would be cus_K8Rd0JsCEsUbNh

signal lindenBOT Apr 19, 2023, 2:14 PM

#

plush mortar Apr 19, 2023, 2:23 PM

#

Its taking a while to look at how exactly the connection was made as it was back in January 2, 2019

#

Just to confirm something quickly, this acct_0JMW53soKKKIrdr2RkEc is your platform account ID correct?

muted sable Apr 19, 2023, 2:32 PM

#

Yes

#

Sorry, should have included that

plush mortar Apr 19, 2023, 2:35 PM

#

Gotcha. Dispute was created for a standard payment created by the connected account acct_1DoGjjESRuzkqMtU

looking deeper into our logs for the connected account it was created your platform (client application ca_6TnY8NGHZ8e6v6vcuzpd5BQqbX2yK4rT) in 2019

That's how it is connected to your platform today

#

and that's why you're receiving the events

#

does that help clarify things?

muted sable Apr 19, 2023, 2:39 PM

#

I'm not sure. I will have to check with the team. You are saying that the account acct_1DoGjjESRuzkqMtU was created by our platform account?

plush mortar Apr 19, 2023, 2:40 PM

#

yup

muted sable Apr 19, 2023, 2:40 PM

#

Interesting

#

I'm wondering if this is something odd in the Spreedly integration. I also have them in our records as onboarding in 2019, but that was over a year before we started using Connect

plush mortar Apr 19, 2023, 2:43 PM

#

Not sure to be honest.. Since the request would have been in 2019, there's no way for us to check where exactly it came from.
I can only see the application that made the request

muted sable Apr 19, 2023, 2:44 PM

#

Related question—is there a way to only receive dispute notifications for transactions that were initiated using destination charges?

#

I.E. those actually created through Connect

plush mortar Apr 19, 2023, 2:45 PM

#

destination charge objects are created on the platform though
so you wouldn't be getting these events as connect events. It would be a direct event instead

muted sable Apr 19, 2023, 2:46 PM

#

Oh, right. Sorry. We have two endpoints, one listening to the direct ones, and one to Connect. So if we wanted to filter on our end, it would be the disputes coming in directly?

plush mortar Apr 19, 2023, 2:47 PM

#

So if we wanted to filter on our end, it would be the disputes coming in directly?
Yup but that would also include any charges that the platform creates without using connect.

muted sable Apr 19, 2023, 2:48 PM

#

Gotcha, so that's also any disputes initiated by clients that we charge directly not using destination charges

plush mortar Apr 19, 2023, 2:49 PM

#

Yup basically non-connect payments.
You'd likely need to check if there's a destination set for the underlying PaymentIntents if you only want the connect payment disputes.

muted sable Apr 19, 2023, 2:52 PM

#

Thanks. All of the charges that we are initiating for our Connect integrated accounts are using destination charges and not standard payments, so that should work.

#

One last question: is it possible to disconnect that account, or is it permanently connected since it shows as created by our platform account?

plush mortar Apr 19, 2023, 2:58 PM

#

Not sure how the account was originally connected to the platform but if it used Oauth flow then you could revoke the access like
https://stripe.com/docs/connect/oauth-reference#post-deauthorize

muted sable Apr 19, 2023, 2:59 PM

#

Okay. I don't think we used that flow, so it would stay connected in this case I guess

plush mortar Apr 19, 2023, 3:00 PM

#

yeah with standard accounts, they need to deauthorize the apps from their end

#

I need to step away now but @limber mirage should be able to help should you have any follow ups!

muted sable Apr 19, 2023, 3:06 PM

#

Thanks, I think that's all for now.

#

Checked with our team, and there was a point I was not aware of where we were automatically creating Stripe accounts for new clients, so this would be one of those accounts. Thanks for the endpoint clarification—that should let us filter the events as needed.

#CalebR