Holdfast
How it works

Stripe · received 18 Oct 2026, 12:18:35 IST

Payment received · ₹250 from Rohan · Cardamom chai, 250 g

Held safely

The message arrived in a new layout

Stripe changed the layout of its messages, and Chai & Co. still expects the old one, so it couldn't read this one. It's kept safe here and can be sent again once that's fixed.

Explained by Holdfast's built-in rules. The AI model did not answer, so this is the rule-based answer.

Is it really from Stripe?

Yes. Its signature matched, so it really came from Stripe.

What happened on each try

  1. Try 1 · Bad Request (400)The app turned it away, and sending the same thing again won't help, so it is held safely.
  2. Try 2 · Bad Request (400)The app turned it away, and sending the same thing again won't help, so it is held safely.

What changed since the last one that worked

  • data.object.customer added
  • data.object.customer.id added
  • data.object.customer_id removed

Send it again

Holdfast first checks it is genuine and hasn't already been delivered.

For your developer

Stripe now sends data.object.customer.id instead of data.object.customer_id, and the app still reads the old field. Read the new one (or accept both), deploy, then resend the held events.

Cause payload_changed

The raw message

Headers

Accept-Encoding
gzip
Content-Length
342
Content-Type
application/json; charset=utf-8
Stripe-Signature
t=1792306115,v1=eb71d87b0d197fcc26809501cb81503eec9511aa74ea373d4b052384fcb29955
User-Agent
Stripe/1.0 (+https://stripe.com/docs/webhooks) holdfast-demo

Body

{
  "id": "evt_3hm0k2yetjja6",
  "object": "event",
  "type": "payment_intent.succeeded",
  "created": 1792306115,
  "livemode": false,
  "data": {
    "object": {
      "id": "pi_3dqyrfrcvdnrg",
      "object": "payment_intent",
      "amount": 25000,
      "currency": "inr",
      "customer": {
        "id": "cus_cuo9wcc61f35"
      },
      "status": "succeeded",
      "metadata": {
        "customer_name": "Rohan",
        "item": "Cardamom chai, 250 g"
      }
    }
  }
}

Last answer from Chai & Co.

{"error":"missing required field customer_id"}