IVOBOT | Stripe Developers | Page 1

dusk bronzeBOT Mar 21, 2023, 10:37 AM

#

safe locust Mar 21, 2023, 10:38 AM

#

Hi there!

#

Can you clarify when/where you get errors? Is it when you make an API request to Stripe? If so can you share the request ID (req_xxx)?

snow hull Mar 21, 2023, 10:39 AM

#

"Webhook payload must be provided as a string or a Buffer (https://nodejs.org/api/buffer.html) instance representing the raw request body.Payload was provided as a parsed JavaScript object instead.
Signature verification is impossible without access to the original signed material.
Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing"

GitHub

GitHub - stripe/stripe-node: Node.js library for the Stripe API.

Node.js library for the Stripe API. . Contribute to stripe/stripe-node development by creating an account on GitHub.

#

The code I use:

    const sig = request.headers['stripe-signature'];
  
    let event;
  
    try {
      event = stripe.webhooks.constructEvent(request.body, sig, endpointSecret);
    } catch (err) {
        console.log(err.message)
      response.status(400).send(`Webhook Error: ${err.message}`);
      return;
    }
  
    // Handle the event
    switch (event.type) {
      case 'payment_intent.succeeded':
        const paymentIntentSucceeded = event.data.object;
        // Then define and call a function to handle the event payment_intent.succeeded
        break;
      // ... handle other event types
      default:
        console.log(`Unhandled event type ${event.type}`);
    }
  
    // Return a 200 response to acknowledge receipt of the event
    response.send();
  });```

safe locust Mar 21, 2023, 10:40 AM

#

So you are getting this error trying to verify the signature of a webhook event?

snow hull Mar 21, 2023, 10:41 AM

#

Yes

dusk bronzeBOT Mar 21, 2023, 10:43 AM

#

snow hull Mar 21, 2023, 10:44 AM

#

Also received a lot of 400 responses on the Stripe Dashboard (received events)

safe locust Mar 21, 2023, 10:44 AM

#

This is a common error when using Node.js

snow hull Mar 21, 2023, 10:44 AM

#

Oh

safe locust Mar 21, 2023, 10:44 AM

#

Have you tried looking into the solutions mentionned here: https://github.com/stripe/stripe-node/issues/341

snow hull Mar 21, 2023, 10:45 AM

#

I think I may've tried it

snow hull Mar 21, 2023, 10:45 AM

#

safe locust Have you tried looking into the solutions mentionned here: https://github.com/st...

So what's essentially the solution if it's so common?

safe locust Mar 21, 2023, 10:46 AM

#

The solution is to make sure you are using the raw body. How to do that depend on many factors. That's why I recommend checking the link above.

snow hull Mar 21, 2023, 10:46 AM

#

Okay

#

But I don't really know how to execute it this way. I mean my app is really simple, so it's main purpose is getting payments and receiving this webhook.

naive parcel Mar 21, 2023, 10:47 AM

#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

snow hull Mar 21, 2023, 10:49 AM

#

Hm?

naive parcel Mar 21, 2023, 10:49 AM

#

sorry I thought my colleague already answered your question

#

let me catch up

snow hull Mar 21, 2023, 10:59 AM

#

This solution doesn't work, still getting 400 responses, although payment goes through.

naive parcel Mar 21, 2023, 11:04 AM

#

would you mind sharing any event ID?

#

evt_xxx

snow hull Mar 21, 2023, 11:20 AM

#

eg

evt_1Mo2ydLqyuD0FDRd9Uv3ta8K

naive parcel Mar 21, 2023, 11:21 AM

#

are you using stripe listen --forward-to ...?

snow hull Mar 21, 2023, 11:22 AM

#

emm, I am using the official Stripe vs code extension based on Stripe CLI

naive parcel Mar 21, 2023, 11:22 AM

#

which one?

#

how are you testing your webhook?

snow hull Mar 21, 2023, 11:22 AM

#

listen --forward-to http://localhost:4242/webhook --forward-connect-to http://localhost:4242/webhook

#

But yes

#

as i can see on the cli

#

it is the --forward-connect-to

naive parcel Mar 21, 2023, 11:24 AM

#

please remove the --forward-connect-to

snow hull Mar 21, 2023, 11:25 AM

#

okay

naive parcel Mar 21, 2023, 11:25 AM

#

this is important if you're listening to the Connect Account events

#

which stripe-cli version you have?

snow hull Mar 21, 2023, 11:26 AM

#

i suppose the newest, because I downloaded it yesterday via homebrew

#

Still:

2023-03-21 12:26:43 --> checkout.session.completed [evt_1Mo3KxLqyuD0FDRdoUO1mrVm]
2023-03-21 12:26:43 <-- [400] POST http://localhost:4242/webhook [evt_1Mo3KxLqyuD0FDRdoUO1mrVm]

#

And

#

No webhook payload was provided.
No webhook payload was provided.
No webhook payload was provided.
No webhook payload was provided.

#

on the "node"

naive parcel Mar 21, 2023, 11:35 AM

#

would you mind adding a console.log(request.body)

#

before the event = stripe.webhooks.constructEvent(request.body, sig, endpointSecret)

snow hull Mar 21, 2023, 11:39 AM

#

okay

dusk bronzeBOT Mar 21, 2023, 11:40 AM

#

snow hull Mar 21, 2023, 11:42 AM

#

naive parcel would you mind adding a `console.log(request.body)`

{
id: 'evt_1Mo3YaLqyuD0FDRdU7XLCBu8',
object: 'event',
api_version: '2022-08-01',
created: 1679398848,
data: {
object: {
id: 'cs_test_a1GJrfFtLZTgigvgRrToTLGdCIp0O1Nh9fOjgm9fB4kPFMNyllY74Zu2uz',
object: 'checkout.session',
after_expiration: null,
allow_promotion_codes: null,
amount_subtotal: 3999,
amount_total: 3999,
automatic_tax: [Object],
billing_address_collection: null,
cancel_url: '',
client_reference_id: null,
consent: null,
consent_collection: null,
created: 1679398820,
currency: 'usd',
custom_fields: [],
custom_text: [Object],
customer: null,
customer_creation: 'if_required',
customer_details: [Object],
customer_email: null,
expires_at: 1679485220,
invoice: null,
invoice_creation: [Object],
livemode: false,
locale: null,
metadata: {},
mode: 'payment',
payment_intent: 'pi_3Mo3YLLqyuD0FDRd0F4AUrni',
payment_link: null,
payment_method_collection: 'always',
payment_method_options: {},
payment_method_types: [Array],
payment_status: 'paid',
phone_number_collection: [Object],
recovered_from: null,
setup_intent: null,
shipping_address_collection: null,
shipping_cost: null,
shipping_details: null,
shipping_options: [],
status: 'complete',
submit_type: null,
subscription: null,
success_url: '',
total_details: [Object],
url: null
}
},
livemode: false,
pending_webhooks: 2,
request: { id: null, idempotency_key: null },
type: 'checkout.session.completed'
}
No webhook payload was provided.

steady nebula Mar 21, 2023, 11:52 AM

#

The No webhook payload was provided. implies that your endpointSecret is wrong: https://github.com/stripe/stripe-node/blob/master/test/Webhook.spec.ts#L109

GitHub

stripe-node/Webhook.spec.ts at master · stripe/stripe-node

Node.js library for the Stripe API. . Contribute to stripe/stripe-node development by creating an account on GitHub.

#

Which whsec_xxx are you using?

#

The one from the CLI?

snow hull Mar 21, 2023, 11:52 AM

#

steady nebula The one from the CLI?

yes

#

Double checked it

#

still the same 400 response

steady nebula Mar 21, 2023, 11:58 AM

#

I can't even see endpointSecret var defined in your code

snow hull Mar 21, 2023, 12:00 PM

#

I only sent you a webhook from my code but endpointSecret is defined as a string of a text like this: "whsec_xxx"

steady nebula Mar 21, 2023, 12:04 PM

#

And that whsec_xxx is the one the CLI spits out when you use stripe listen?

snow hull Mar 21, 2023, 12:06 PM

#

yes

steady nebula Mar 21, 2023, 12:06 PM

#

Not sure unfortunately. Maybe your CLI is signed into a different account?

snow hull Mar 21, 2023, 12:29 PM

#

No, because I do receive the same responses on the dashboard

steady nebula Mar 21, 2023, 12:30 PM

#

Well the CLI doesn't log responses in the Dashboard

snow hull Mar 21, 2023, 12:31 PM

#

I mean I think it is the according 400 response

#

Bc of the same event Id etc.

steady nebula Mar 21, 2023, 12:36 PM

#

Which evt_xxx are you looking at?

#

The CLI doesn't log any webhook errors in your Dashboard. They'll all appear as successful

snow hull Mar 21, 2023, 12:59 PM

#

#

Something like this

brazen raptor Mar 21, 2023, 1:27 PM

#

Hi 👋 apologies for the delay, taking over for my teammates.

#

Looks like there is quite a bit of context in this thread and the focus has moved around. Would you mind summarizing for me the current state of your concern/problem?

snow hull Mar 21, 2023, 1:36 PM

#

Well, I'm not super fluent at it, but there's some sort of an issue with my webhook, because of it's body (which is undefined for some reason, but then it returns the correct state of checkout.session) or a key (which we excluded I suppose). I am constantly getting results 400 or 404 upon the arrival of the response from webhook.

#

And the main thing is that the code I am using is straight from the Stripe dashboard, so there should not be any issue, yet I can't do anything on my server precisely and only after the payment has succeeded (because the webhooks doesn't seem to work properly).

brazen raptor Mar 21, 2023, 1:41 PM

#

Webhooks do not block payments, nor are they expected to.

snow hull Mar 21, 2023, 1:41 PM

#

The main issue is "No webhook payload was provided." I think. As said before, there might be a problem with formatting of the body, but it's the code from the dashboard and I am not that fluent with webhooks

snow hull Mar 21, 2023, 1:42 PM

#

brazen raptor Webhooks do not block payments, nor are they expected to.

Correct, but they are the only way to execute some code only when the payment was successful (as the Stripe docs and support said, you should not implement it via success_url).

brazen raptor Mar 21, 2023, 1:43 PM

#

Correct, webhooks are the preferred route for triggering after payment actions to avoid running into incomplete flows if a customer suddenly loses connection after triggering a payment.

Where are you seeing the No webhook payload was provided message being raised?

snow hull Mar 21, 2023, 1:45 PM

#

During this debugging with people before you we added some console.logs to the try catch

#

So

#

here:

#

try {
        console.log(request.body)
      event = stripe.webhooks.constructEvent(request.body, sig, process.env.STRIPE_WEBHOOK_SECRET);
    } catch (err) {
        console.log(err.message)
        response.status(400).send(`Webhook Error: ${err.message}`);
      return;
    }

brazen raptor Mar 21, 2023, 1:47 PM

#

So it's being thrown by that log in the catch block? Can you share your larger code snippet? I see you're referencing request.rawBody in your constructEvent call, but I don't recall seeing that defined in your previous code that you shared.

snow hull Mar 21, 2023, 1:49 PM

#

Yeah, a small mistake. It was supposed to be "body". Still doesn't work tho.

brazen raptor Mar 21, 2023, 1:51 PM

#

Same error or different one?

snow hull Mar 21, 2023, 1:52 PM

#

Same one

#

I mean response 400

#

2023-03-21 14:48:48 --> checkout.session.completed [evt_1Mo5YSLqyuD0FDRd7K3s3DlF]
2023-03-21 14:48:48 <-- [400] POST http://localhost:4242/webhook [evt_1Mo5YSLqyuD0FDRd7K3s3DlF]

#

Webhook payload must be provided as a string or a Buffer (https://nodejs.org/api/buffer.html) instance representing the raw request body.Payload was provided as a parsed JavaScript object instead.
Signature verification is impossible without access to the original signed material.
Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

GitHub

GitHub - stripe/stripe-node: Node.js library for the Stripe API.

Node.js library for the Stripe API. . Contribute to stripe/stripe-node development by creating an account on GitHub.

brazen raptor Mar 21, 2023, 1:55 PM

#

Okay, so a different error.

snow hull Mar 21, 2023, 1:56 PM

#

Right, but there's still something with the body, as I assume the key is correct (as it is the same as the one from CLI and Dashboard).

brazen raptor Mar 21, 2023, 1:58 PM

#

Try adding this to set up bodyParser to give you both the parsed body and the raw one:

  verify: (req, res, buf) => {
    req.rawBody = buf
  }
})); ```

Then can you try referencing `request.rawBody` as you had before?

snow hull Mar 21, 2023, 1:59 PM

#

okay

#

require('dotenv').config();

const express = require('express');
const app = express();
const cors = require('cors');
const { createClient } = require('@supabase/supabase-js');
const {bodyParser} = require("body-parser")

app.use(express.json());
app.use(cors({
    origin: 'http://localhost:3000',
}));

app.use(bodyParser.json({
    verify: (req, res, buf) => {
      req.rawBody = buf
    }
  })); 

const stripe = require('stripe')(process.env.STRIPE_PRIVATE_KEY);

#

Is this the correct place?

#

app.use(bodyParser.json({
^

TypeError: Cannot read properties of undefined (reading 'json')

#

Something wrong

brazen raptor Mar 21, 2023, 2:02 PM

#

Ah, you had:
app.use(express.json());
which I believe would have parsed all your request bodies to JSON.

Do you need the JSON parsing for another part of your process? If not I'd suggest removing what I suggested, removing the line I referenced above, and then try running it again.

snow hull Mar 21, 2023, 2:03 PM

#

ou

#

so this might've been an issue

#

Yeah, but I fetched product from the frontend as an object (added handler to the post)

#

Yay

#

I think

#

something is fixed

#

What does this handler mean, btw? And why it acts so strange?

brazen raptor Mar 21, 2023, 2:09 PM

#

Can you elaborate?

snow hull Mar 21, 2023, 2:09 PM

#

Oh wait, theres still some issue

#

2023-03-21 15:05:50 <-- [200] POST http://localhost:4242/webhook [evt_3Mo5oiLqyuD0FDRd0TyrBL03]
2023-03-21 15:05:50 --> charge.succeeded [evt_3Mo5oiLqyuD0FDRd0T6C4zXS]
2023-03-21 15:05:50 <-- [200] POST http://localhost:4242/webhook [evt_3Mo5oiLqyuD0FDRd0T6C4zXS]
2023-03-21 15:05:51 --> checkout.session.completed [evt_1Mo5oxLqyuD0FDRdEjtj3b3j]
2023-03-21 15:05:51 <-- [200] POST http://localhost:4242/webhook [evt_1Mo5oxLqyuD0FDRdEjtj3b3j]
2023-03-21 15:08:21 --> payment_intent.requires_action [evt_3Mo5rMLqyuD0FDRd1YtUsca7]
2023-03-21 15:08:21 <-- [200] POST http://localhost:4242/webhook [evt_3Mo5rMLqyuD0FDRd1YtUsca7]
2023-03-21 15:08:21 --> payment_intent.created [evt_3Mo5rMLqyuD0FDRd1Waq9OQs]
2023-03-21 15:08:21 <-- [200] POST http://localhost:4242/webhook [evt_3Mo5rMLqyuD0FDRd1Waq9OQs]
2023-03-21 15:08:33 --> payment_intent.succeeded [evt_3Mo5rMLqyuD0FDRd1euIdAvH]
2023-03-21 15:08:33 <-- [500] POST http://localhost:4242/webhook [evt_3Mo5rMLqyuD0FDRd1euIdAvH]
2023-03-21 15:08:33 --> charge.succeeded [evt_3Mo5rMLqyuD0FDRd1SbRVY6D]
2023-03-21 15:08:33 <-- [200] POST http://localhost:4242/webhook [evt_3Mo5rMLqyuD0FDRd1SbRVY6D]
2023-03-21 15:08:33 --> checkout.session.completed [evt_1Mo5rZLqyuD0FDRdSQzHKoMC]
2023-03-21 15:08:33 <-- [200] POST http://localhost:4242/webhook [evt_1Mo5rZLqyuD0FDRdSQzHKoMC]

#

the only one event i care about (succeeded) is 500

#

ugh

brazen raptor Mar 21, 2023, 2:12 PM

#

That 500 indicates your code crashed while trying to handle the Event that it received, you'll need to debug the code that is handling your Events to determine why.

snow hull Mar 21, 2023, 2:12 PM

#

okay

#

how can I transfer product parameters from payment handling to the webhook?

brazen raptor Mar 21, 2023, 2:16 PM

#

You'll need to get to the higher-order object that contains Product references. Looks like you're using Checkout Sessions, so that is probably what you're looking for.

You'll either want to retrieve the Checkout Session that is associated with the Payment Intent in the Event you're handling (if you continue to work with Payment Intent Events), or you pivot to listening to Checkout Session events such as checkout.session.completed.

snow hull Mar 21, 2023, 2:28 PM

#

Okay, but I do not have all the product info inside the Checkout Session. Can I add some additional JSON Object to the Checkout Session on its creation?

brazen raptor Mar 21, 2023, 2:29 PM

#

Oh, so when you say Product info, you aren't referring to Product objects that you're using?
https://stripe.com/docs/api/products

If so, you're probably want to leverage metadata:
https://stripe.com/docs/api/metadata

snow hull Mar 21, 2023, 2:30 PM

#

Or should I just ask: what is the preferable way of accessing the bought product after the payment succeeded

snow hull Mar 21, 2023, 2:31 PM

#

brazen raptor Oh, so when you say Product info, you aren't referring to Product objects that y...

Yes

#

Because I need the user id from my database (which is acquired on creation of checkout session) in order to add the new product to his records after the payment

brazen raptor Mar 21, 2023, 2:33 PM

#

If you aren't using Products and referencing those objects, then you'll need to provide your own product information/context. The best way to do that is via metadata which lets you store key-value pair data on Stripe objects, that you can then reference later.

snow hull Mar 21, 2023, 2:36 PM

#

Okay, maybe let's clear things up. The user clicks "buy" and gives my backend his ID, product ID and some other parameters. Then the product ID is used by checkout session in order to process payment (first it gets the product data from my DB and then this data is added to the checkout session) and then after successful payment I want to pushItem() to my DB (which should be done via webhooks), and the pushItem needs user Id, product Id and the other parameters from the first step of this whole process.

#

How can I retrieve these parameters in the most effective way possible? I don't necessarily want stripe to have it all on their server as it may be a lot of data or data in a unfavorable way (JSON Object). What approach should I choose?

#

Or what do you propose?

#IVOBOT