#pavlos_webhooks

1 messages · Page 1 of 1 (latest)

austere mortarBOT
#

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

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

unborn lagoon
#

Hello! Can you give me the ID of a specific Event you expected to be delivered to your Webhook Endpoint in test mode?

sudden kestrel
#

"py_3PItm8I2bimlkKHb1Df6lGUo"

#

we also deleted the previous webhook and made a brand new one which also did not work

unborn lagoon
#

That's not an Event ID. Event IDs start with evt_.

sudden kestrel
#

evt_3PItm8I2bimlkKHb1YNUSM0d

amber muskBOT
unborn lagoon
#

Looking at your account, the main issue seems to be that you don't have a regular Webhook Endpoint set up, you only have Connect Webhook Endpoints. Connect Webhook Endpoints will only receive Events from connected accounts, not your own account. The Event in question is on your account, not a connected account.

sudden kestrel
#

can both be selected simultaneously? do I have to remake the webhook to fix?

calm hornet
#

👋 you can set the same URL for both types of webhook but we generally recommend keeping them separate for simplicity

sudden kestrel
#

I see thank you

#

that should suffice for now

calm hornet
#

👍

sudden kestrel
#

one followup question: any payment made through an instance of our SDK would be associated with "account" and not "connected account"?

calm hornet
#

It depends. Are you creating direct charges or destination charges?

Any requests made with stripe-account header set to a connected account ID will result in that request being associated with that connected account. See: https://docs.stripe.com/connect/authentication#stripe-account-header

So if you're creating the PaymentIntents while setting stripe-account header then it will be associated with the connected account

sudden kestrel
#

we are creating the PaymentIntent via our backend by calling the Stripe SDK in the following way:

 Stripe::PaymentIntent.create(
              @kwargs,
              { stripe_account: @merchant.account_id }
            )
#

@kwargs include amount, currency, payment_method_types, setup_future_usage_statement_descriptor_suffix, and metada

#

the SDK seems to be initialized by just setting the Stripe.api_key; there doesn't appear to be any headers being sent

#

does passing a stripe_account id like we do associate as a connected account? or our account?

calm hornet
#

You are setting the connected account ID here
{ stripe_account: @merchant.account_id }

#

yes

sudden kestrel
#

I see, so in that case we need to set up both a connected account webhook, and an account webhook (specifically for testing)

calm hornet
#

Correct

sudden kestrel
#

is it still recommended they use seperate endpoints?

#

I imagine this is because the verification would initially fail for whichever wasn't checked first?

calm hornet
#

I imagine this is because the verification would initially fail for whichever wasn't checked first?
I'm not sure what you mean by that.

is it still recommended they use seperate endpoints?
It is upto your usecase really but general recommendation with connect is to use different URLs