@4samy
That error message is not indicative of a problem within the plug-in. More than likely you are using the same stripe account across multiple websites. Stripe sends webhook events to all of the configured webhook URLs for an account.
So when you receive an order on website A, Stripe sends the same webhook event to website A and B if there are webhook urls for them.
That is why Stripe recommends that you have one website per account. Adding a new account is trivial, all you have to do is click the add account option in the upper left-hand corner of the stripe.com dashboard.
Kind regards
Thank you for following up on this issue
These requests are from an application built on the flutter platform
Depends on your plugin
With only one website
Depends on your plugin
With only one website
Can you please clarify what you mean by that statement?
When I say one website for an account I am referring to one e-commerce website. That is the website where the order is originating from. If you have multiple websites that are creating orders, stripe is going to send webhooks to each one of those websites. Of course this is not an issue if you have multiple websites configured for separate processes like a fulfillment website that is receiving instructions, not generating an order.
-
This reply was modified 3 years, 8 months ago by
Clayton R.
I mean I don’t have more than one website, it’s only one website
Why is this error happening to me?
Why is this error happening to me?
I’ll need some help from you in order to a best answer that question.
Are you modifying the order_id property of the metadata perhaps or removing metadata using the Stripe plugin filters?
Are you testing on a localhost like a laptop? If you’re using the same Stripe account for doing test orders on a local machine or a staging website, then the webhook is going to the url configured for the account.
If you go to the stripe.com > developers > events page you can see the webhook that triggered that log entry. Look at the body of the request, specifically the metadata. Is there an order_id property in the metadata?
Are you modifying the order_id property of the metadata perhaps or removing metadata using the Stripe plugin filters?
No
Are you testing on a localhost like a laptop? If you’re using the same Stripe account for doing test orders on a local machine or a staging website, then the webhook is going to the url configured for the account.
No
If you go to the stripe.com > developers > events page you can see the webhook that triggered that log entry. Look at the body of the request, specifically the metadata. Is there an order_id property in the metadata?
Yes
but “order”: null,
The order ID being null is the source of your problem. What payment method is this for? Is it just credit cards or is it a local payment method?
The Stripe Plugin always populates the order ID metadata. So the fact that it is null is very strange. The stripe plug-in never processes a payment unless there is an order because that’s where all the information comes from. So there is definitely an order somewhere.
Of all the tens of thousands of merchants we have we’ve never had this issue reported so I’d recommend taking a closer look at all of the plug-ins you’re using. Or see if you have some custom snippet of code.
That webhook is only relevant for non card payments. It’s not needed for credit cards.
