#Yoshi-webhook

1 messages · Page 1 of 1 (latest)

sand imp
#

Can you share with me your merchant ID? you can find it from the Stripe Dashboard -> Settings ->Account Details

fallow cipher
#

@sand imp I have sent you the marchant ID directly via DM.

sand imp
#

You can share the merchant ID in this chat, only Stripe engineers can access your account details.

fallow cipher
#

I see that MARCHANT_ID was safe data to share here. So we will share it again.

acct_1KJu4NF8jJT1UsIp

sand imp
#

Thanks, let me take a look

#

Seems like we have a timeout error here

#

Can you check if this webhook endpoint is currently working?

fallow cipher
#

We used Postman to perform POST communication, and CloudWatch confirmed that there was an access. (This is an error log because I did not specify any parameters, etc.)

sand imp
#

Can you also send me the POSTMAN command so that I can test it out at my end as well?

fallow cipher
#

https://test.jobns.jp/payments/webhook

This is what we were testing.
We will address this after we have completed testing with Postman, as we need to redeploy to add the Allow List. Could you please contact us again?

#

Tests should be performed via POST communication.

sand imp
#

BTW I'm getting the same timeout error in POSTMAN

fallow cipher
#

Sorry, I now fully understand the cause of the problem with the current test results.....
It is caused by the IP restrictions set on the AWS load balancer side. As you pointed out, we needed to allow IP addresses.

#

We apologize for the time you have spent on this issue, even though it was caused by something other than Stripe.

sand imp
#

No problem! I'm happy to know that you've found out the root cause of the problem.

#

Don't worry about it! We are happy to help!

fallow cipher
#

Regardless of this matter, we are always very grateful for the generous development support we receive. We look forward to working with you again in the future!