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

Payment received · ₹200 from Ishaan · Assam CTC, 1 kg

Held safely

The signature didn't match

Holdfast couldn't confirm this really came from Stripe, so it kept it aside instead of passing it on. Nothing has been lost.

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?

Not confirmed. The signature didn't match, so it may not be from Stripe. Holdfast did not pass it on.

What happened on each try

Not tried yet.

What changed since the last one that worked

Nothing. It has the same layout as the last one Chai & Co. accepted.

Send it again

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

For your developer

Check that the signing secret configured in Holdfast matches the one in the Stripe dashboard. If it does, this request may not be from Stripe.

Cause signature_mismatch

The raw message

Headers

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

Body

{
  "id": "evt_1ln054bl28dfz",
  "object": "event",
  "type": "payment_intent.succeeded",
  "created": 1792306235,
  "livemode": false,
  "data": {
    "object": {
      "id": "pi_1ab98im5dj63y",
      "object": "payment_intent",
      "amount": 20000,
      "currency": "inr",
      "customer_id": "cus_exe9ytpp5dyn",
      "status": "succeeded",
      "metadata": {
        "customer_name": "Ishaan",
        "item": "Assam CTC, 1 kg"
      }
    }
  }
}