#cogwash
timid robinBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- cogwash, 49 minutes ago, 6 messages
dense mural
You can share it here and I can raise it internally. Or you can write in to Support with suggestions: https://support.stripe.com/contact
Low-code integrations with fully hosted checkout sessions /always/ require some reference (e.g. an order id) to be passed along with webhook events (which may arrive days later). Your example code for creating a checkout session should include a 'payment_intent_data' => 'metadata' property that demonstrates how this is done. I spent an entire day searching for a solution and ended up finding a hint on Stackoverflow. This information should be in-the-face from the start.
quoting here
Low-code integrations with fully hosted checkout sessions /always/ require some reference (e.g. an order id) to be passed along with webhook events
This is not a requirement
frigid compass
But it's a very frequent use case. Events need to be associated with some local data. Otherwise why would anyone listen to events in the first place.
dense mural
That is not necessary for every integration.
frigid compass
Ok, I may be looking at it from a commerce platform perspective. Still, a hint under the example would be helpful.
dense mural
That I can understand. It seems to me this would be most applicable in the section of the docs on Fulfilling the order: https://stripe.com/docs/payments/checkout/fulfill-orders#fulfill
I can make a suggestion that we include a note about using metadata to set a reference ID that you can then retrieve in the webhook event.