#naril_webhooks

1 messages · Page 1 of 1 (latest)

haughty brambleBOT
#

👋 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/1470720024804327507

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

neat field
#

hi

full orchid
#

That should receive the configured event types from accounts that have installed the app

neat field
#

i need you to help me to put some order here please

#

i see webhook configuration in the stripe-app.json, i see also webhooks config in my account -> webhooks -> create destinations (here i have 2 options: 1) Your account; 2) Connected Accounts.
i have created webhooks desinations as Connected Accounts and i configured 2 url (per payload style: snapshot and thin)

#

i tried to install, uninstall, create payment_link and nothing, no webhook events called

full orchid
#

Can you share an evt_xxx ID for an event you expect to be sent to a webhook?

neat field
#

sure but guide me how to give it to you

full orchid
#

Let's just started with the plink_xxx ID for the Payment Link you created

neat field
#

plink_1SzDCXHAH1Jf6DrMhC7PXpeE

full orchid
#

evt_1SzDCXHAH1Jf6DrM3uQhD1Fc is the ID of the payment_link.created event

Looks like it fired on this account: acct_1Sjfj3HAH1Jf6DrM

#

What's the acct_xxx ID of the account that publishes the app?

neat field
#

acct_1Sjfj3HAH1Jf6DrM -> this is my sandbox account

#

i don't have live account

full orchid
neat field
#

oh

#

wait give me to summarize it to make sure i undestand it right

full orchid
#

The events will just send to a normal webhook as they're firing on the same account, not a different account (that has installed the app)

neat field
#
  1. so in my stripe-app.json i don't need the webhooks section
  2. i have created a connected account webhooks so i will not get events from my account (this is why i can create "Your account" destination)
  3. to really test it i need to install the app in other account - can be also sandbox? how do i install it in other account (i can't do it public since i don't have live account)
full orchid
neat field
#
  1. probably something that Opus made up 😂
  2. cool
  3. ok cool i will try it
#

"If you don’t see the External test tab, verify if you’ve selected public distribution from Create a release."

#

i don't have live account, so i don't see External test tab

#

public distribution is not allowed if we don't have live account - this is what i understood

full orchid
#

If you intend to publish the app, you're going to need a live account before you can do that so then you can do an external test

neat field
#

ok... so the hard truth is that i cannot test and expreience it...

full orchid
#

Not end-to-end as an actual installer/user without a live account, no

neat field
#

ok, so also i can't verify signature (secured) when mocking events from CLI

full orchid
#

You should be able to, yes

neat field
#

how?

full orchid
#

The CLI has it's own signature secret it'll print out when you do stripe listen

#

Ready! Your webhook signing secret is '{{WEBHOOK_SIGNING_SECRET}}' (^C to quit)

neat field
#

i already have a backend implemented so i dont really need stripe listen. maybe my best shot here is to test the app right now when the destination is "Your account"

#

WDYT?

full orchid
#

The listen function doesn't replace your backend, it actually just forwards events to it

#

So you can test the Connect webhook endpoint without having to actually install the app

#

I recommend you stop chatting with Claude and read the documentation

neat field
#

😂

full orchid
#

You're conflating different concepts

full orchid
neat field
#

alright, i will just use the Your account, its simpler

#

thanks

#

one more question please

#

are you here?

full orchid
#

Sure

neat field
#

when merchant installed the application it become a connected account?

#

no need for oauth / RAK for webhooks?

full orchid
neat field
#

COOL!

#

but i do need RAK / OAuth to be able to execute queries from ny backend to stripe on merchants behalf

full orchid
#

The 'connection' facilitated when they install the app enables you to make API requests to Stripe on their account

#

But otherwise it's easier to just use your account's key with the stripeAccount param

neat field
#

wow!
so you are telling me that i am using my account stripe api key and i put the merchant that installed my app in the Stripe-Account and it will work?

full orchid
#

Yep, should do

neat field
#

"should" you are not sure?

full orchid
#

That's how it works yes, assuming the account has installed the app and you've configured the permissions correctly in your app manifest

#

But you've no way to test it because your app is not public

neat field
#

yeah... i will create live account soon. thank you very much for your help!

haughty brambleBOT
neat field
#

hi, can i have another one?

full orchid
#

Sure

neat field
#

great!
when creating connected account webhook destination i need to provide 2 urls for both payload styles. but when creating your account destination i don't

#

it still will be consistant? (both payloads types will arrive to the same ednpoint, how i should to distingush between them?)

full orchid
#

Will what be consistent?

full orchid
neat field
#

in my "Your account" definition can i split it also to 2 different endpoints?

#

wierd because i can select specific event per payload style

full orchid
neat field
#

in your account i can select anything

full orchid
#

Why do you want/need both?

neat field
#

i don't know what i will get because seems like Stripe tret them differently

#

(in connected accounts)

#

(the selection is limited there)

full orchid
#

I recommend just using the non-thin events. Thin events are currently only valid for V2 APIs which you're not using

neat field
#

so i will get snapshot payloads?

full orchid
#

Yes

neat field
#

so thin is "not relevant"?

#

also in connected account, all events will be sent as snapshot?

full orchid
#

I would say not, but ultimately this is your integration

full orchid
neat field
#

when i configured it seems like i must define 2 urls (per payload style)

#

i prefer one (simplest)

full orchid
#

You must have a V2 event type selected

neat field
#

i didn't understand it

#

ohhh

#

now i get it

full orchid
#

Don't understand what? When you create the webhook endpoint in the Dashboard, you select the 'types' of events you want to receive. Depending on what you select there, you will be required to add a 'thin' event enpoint/URL (e.g. anything with v2 after it)

Screenshot_2026-02-10_at_11.47.34.png
neat field
full orchid
#

If you select both v2 and normal events, then you'll need to provide two endpoints/URLs

neat field
#

ohhhh

#

you are the B-E-S-T!!! thank you!!!

full orchid
#

Then can obviously be the same URL, but then you'll likely have more convoluted logic to handle the different payloads

neat field
#

cool!

#

i have another one 🙂

#

i have ai agent that that will fetch data with Stripe MCP server on my users (merchants) behalf. the auth header should be my api key and i need to include the account id in the header? like a standard backend request?

full orchid
neat field
#

ohhhhh greatttt