#soumya_webhooks

1 messages · Page 1 of 1 (latest)

jovial valeBOT
#

đź‘‹ Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1509622466866057396

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

unborn patio
#

hello! can you share an example payment intent ID or customer ID?

#

i'm assuming those are the 2 event types you're listening for now?

#

or at least trying to listen to?

wet quiver
#

I will share now

#

cus_UbEO61OXcXTFCx

#

Firstly can you clear which type we should subscribe your account or connect account?

unborn patio
#

it depends on how you're creating objects, which is why i asked for an example

#

if you're creating them on your platform account, you listen to the account webhook. if you create them directly on a connected account (via the stripe-account header) you listen to the connect webhook

wet quiver
#

We are from loyalty juggernaut we are building gravty Loyalty public app.so can you tell me how to register that webhooks?

unborn patio
#

for that customer, it looks like it was created directly on the account acct_1TTGDcQKIM63L2qi (i'm assuming that's your platform?)

wet quiver
#

Yes

unborn patio
#

can you read through this doc real quick and confirm which type of charge you're doing for your integration? direct / destination / separate charges and transfers

wet quiver
#

Actually I explain my usecase suggest me the right case.when merchant install the gravty Loyalty from stripe marketplace we want to sync customers from stripe to gravty

unborn patio
#

this doc also clearly lays out which webhook type you should use based on which integration path you're taking

wet quiver
#

And also can you confirm if any merchant install the app they will become connected account for our platform account??

#

Claude chatgpt every ai tool is telling me the same

unborn patio
#

sorry i think i'll need more details to be able to advise you on your use case, can you explain what exactly you mean by syncing customers? what all are you syncing? what is your app actually doing?

wet quiver
#

Actually we are building loyalty app.if a merchant install the app we listen to customer created event and if we get we enroll then to our platform and user get 500 points.tbry will become part of gravty.

unborn patio
#

also FYI it does look like we're trying to send notifications to your webhook endpoint but we're getting errors in response (you can view details on those delivery attempts here)

wet quiver
#

We will give them points if we get payment intent webhook

#

Some loyalty usecases we are working onn

unborn patio
#

ok so if you're listening to customers that they themselves are creating then you'll definitely want to use the connect webhook

#

but in the example you shared earlier you were creating the customer directly on your platform account, so that's not an accurate simulation of what this would look like in practice

wet quiver
#

Right now we are developing the application

#

We don't have clients yet

#

So for testing purpose I have created in my platform account

#

I don't know how this app can be installed to another account for testing purpose

unborn patio
#

when you say app do you mean you're building a stripe app?

wet quiver
#

Yes

#

Actually we don't have backend webhooks will processed through lamda but in the env I should keep stripe account id as key and gravty config as value then only I can process the points etc.. accordingly but when webhooks are configured through your account I did get any stripe account id

#

I'm struggling to find the way and I'm confused with these stripe connect

unborn patio
#

that won't really represent someone installing your app but it would let you quickly test your webhooks out

wet quiver
#

Can you confirm if any merchant install our app in future they will become connected account for our platform account?

#

?

#

And also currently from the test mode of loyalty juggernaut I have configured the webhooks so those webhooks will trigger if any merchant install the app? Or programatically I need to create in the code? Can you please confirm

#

I need to complete building strip app this end of the week

unborn patio
#

Can you confirm if any merchant install our app in future they will become connected account for our platform account?
sort of - you get resticted abilities to access data on connected accounts based on which permissions your app requests

#

so they don't become full on connected accounts, but you do get limited read / write access including connect webhooks

#

And also currently from the test mode of loyalty juggernaut I have configured the webhooks so those webhooks will trigger if any merchant install the app? Or programatically I need to create in the code? Can you please confirm
not sure what you mean by this, are you just looking for a way to automatically be notified if someone installs the app?

wet quiver
#

Actually we want to configure three webhooksd

jovial valeBOT
wet quiver
#

Customers created updated and payment intent

#

If merchant who installs our app will they automatically subscribed to these events if configured in loyalty juggernaut dashboard or

#

Do we need to programmatically configure webhooks for each merchant in the code itself?

unborn patio
#

no, you just need to set up one connect webhook (or 3 if you really need to create one webhook per event) and listen for those events

wet quiver
#

Is it done in the dashboard?

#

Or programatically??

rancid fog
#

Hi there, taking over for @unborn patio as they had to step away. Catching up on the thread now

wet quiver
#

Thank you

#

Can you answer my question

rancid fog
#

For the last question, if you are asking about creating connect webhook endpoints, that can be done either in the dashboard or programatically via the API. This is discussed here in our docs:
https://docs.stripe.com/connect/webhooks

When you create a webhook in Workbench, assign the scope by setting Events from to Your account or Connected accounts. When you create a webhook using the API, assign the scope by setting the connect parameter to false (for Your account) or true (for Connected accounts).

wet quiver
#

If I configur through dashboard also webhooks will sent foor each merchant who installz our appp???

#

Excuses me?

rancid fog
#

I'm reading through the thread to make sure I understand all the details

#

Based on what I understand for your use case, you can create one Connect webhook endpoint in your dashboard (Developers → Webhooks → "Listen to events on Connected accounts"), and subscribe to customer.created, customer.updated, and payment_intent.succeeded. You don't need to programmatically create webhooks for each merchant. When any merchant installs your app in the future, their events will automatically flow to this single endpoint, with the account field telling you which merchant it came from.

#

You can test this out by creating a test connected account via the Dashboard or API, then create a customer on that connected account using the Stripe-Account header — your Connect webhook should fire.

wet quiver
#

Can I alsoo test payment intent webhook from connected account?

rancid fog
#

Yes, you can test and see that webhook event as well

#

And if you haven't done so already, when configuring your Stripe App, you will need to add the event_read permission, plus any permissions associated with the specific events you want to handle, as described here
https://docs.stripe.com/stripe-apps/events

wet quiver
#

The main problem is that two different Stripe concepts are being mixed together:

  1. Stripe Connect connected accounts
  2. Stripe Apps installed by merchants

These are not the same architecture.

In your current Gravty integration flow, merchants:

  • install your app from the Stripe Marketplace,
  • authorize permissions/scopes,
  • connect their Gravty account through OAuth.

That does not automatically make them Stripe Connect connected accounts.

So the statement:

“When any merchant installs your app in the future, their events will automatically flow to this single Connect webhook endpoint…”

is only true for a real Stripe Connect platform setup.

The issue is:

  • A Connect webhook endpoint (“Listen to events on connected accounts”) only receives events from accounts that are actually onboarded as connected accounts under your platform.
  • A Stripe App installation alone does not create that relationship.

So if your system currently:

  • uses Stripe Apps,
  • uses app scopes/permissions,
  • does not onboard merchants through Stripe Connect,

then:

  • your Connect webhook endpoint will not automatically receive events from all merchants who install the app.

That is the architectural mismatch.

#

Can you suggest good solution? Any merchant installing the app after connecting to our platform webhooks should work

rancid fog
#

It looks like your last message came from an LLM? It doesn't appear to be an accurate statement - this is what our official docs on Stripe Apps state about events:
https://docs.stripe.com/stripe-apps/events

Apps can use Webhooks to get alerts about events happening on their users’ accounts. This helps app developers keep information in sync or trigger actions within their app when something changes.

I would recommend following that guide and test things out to see how everything works for your use case

wet quiver
#

Okay thank you soo much I will try to use connect webhook and if I get any issues I will reach out here