#Manoj Kumar

1 messages · Page 1 of 1 (latest)

harsh craterBOT
wide umbra
#

I'm not familiar with RestLet. Do you integrate Webhook on your own or use third party plugin?

proven grove
#

Own

#

( RestLet is type of java script )

#

no issues for this ,
but plz suggest me how i can, use token (Auth 2.0 / 2.1) in stripe that it can be accessible from stripe

wide umbra
#

Webhook is from Stripe to your server. Stripe doesn't require any token to be set in Stripe. You will only need to create the Webhook endpoint with Stripe. You may refer to Webhook integration guide here: https://stripe.com/docs/webhooks/quickstart

proven grove
#

without Auth token My API can't be access

wide umbra
#

In this case, you'd need to configure your API to allow the access without auth token

proven grove
#

can you give me any sample code for netsuite script V2.1 or 2.0

wide umbra
proven grove
#

ok,
we have already checked these all stuffs

#

can you plz help to understand this error -

"Invalid encoding: ISO-8859-1"

This error comes whenever i try trigger my API ( on webhook )

#

Error mesg: "Invalid encoding: ISO-8859-1"
and error code 405

proven grove
wide umbra
#

Could you share the event ID (evt_xxx) where you see this error?

proven grove
#

not able to find the current event id

but this is on "customer create event" - right now i am trying to resend
but there is no new event_id generated ( all are old)

#

ok i got this:-

evt_1MJy7FSByRRJwx0C4S1JEjY7

#

??

#

hi plz suggest

#

hi plz suggest

wide umbra
#

The discord server is busy. Looking into it now

proven grove
#

ok w8ing for your response

wide umbra
#

Error code 405 - Method Not Allowed is returned from your server. 405 usually indicates that the server knows the request method, but the target resource doesn't support this method. Stripe doesn't have the visibility why your server returned such error. I'd recommend tracing your request to check where it's getting held at.

With regards to "Invalid encoding: ISO-8859-1", this is due to your response header telling us that the content is in charset=iso-8859-1. Stripe is only able to comprehend response in UTF-8.

Stripe only looks for response code 200 for successful delivery. The response body doesn't really matter.

proven grove
#

i know about this -
same webhook is working on postman, then why not in strip- environment
I am sending the same parameter as your system will be sent

#

if this is not possible,
Then give me some other option

#

I also trying to pull customer records
based on created and updated

only getting based on "created date" but not based on "updated date" let me know is this possible ??

#

to get the data based on "updated date" [ data related to customer ]

wide umbra
#

same webhook is working on postman, then why not in strip- environment
I'd recommend changing your server response to UTF-8 format, so that it may surface the correct error message in Stripe dashboard.

Stripe doesn't have the visibility why your server responded so. I'd recommend adding more logs in your server to trace where the error is thrown at.

proven grove
#

as per documents, because STRIP does't sending the headers "Headers: “User-Agent : Mozilla/5.0”

#

that's why we are getting this issues, so plz suggest the alternate way

wide umbra
#

as per documents, because STRIP does't sending the headers "Headers: “User-Agent : Mozilla/5.0”
Stripe doesn't use Mozilla/5.0 for sending webhook as it's not a browser request. The User-Agent for Stripe event will be User-Agent: Stripe/1.0

proven grove
#

😆 - ok means there is no way to reslove this issues

#

its not a good idea. can you give me any alternate way.

My Purpose : to collect all customer records and its metadata, when created /deleted/ updated

#

in netsuite

wide umbra
#

ok means there is no way to reslove this issues
Not sure what you meant. If you wish to receive Stripe events, your server should allow Stripe's user agent

My Purpose : to collect all customer records and its metadata, when created /deleted/ updated
When a customer data is created/updated/deleted via API, you should be able to see those data in the response.

If it's not via API, the the only way is to allow your server should listen to customer events for those data.

proven grove
wide umbra
#

User-Agent is the information about who is making the request. Since Stripe server is the one making the request, why should it include other non-Stripe details

#

Mozilla/5.0 is for browser request that is Mozilla-compatible. Stripe event is not a browser request, but a server request

proven grove
#

Because stripe providing the web-hook features ,
which should must be compatibility with all system. otherwise there is no use of this

#

try to understand and plz help me out

wide umbra
#

User-agent is to share the source of request. Stripe follows the industry standard on the request information. Since the request is made with Stripe server, the user-agent will reflect User-Agent: Stripe/1.0 accordingly and doesn't include incorrect information as it's not a browser request.

I'd recommend removing the user-agent check in your server in order to receive stripe events.