Make.com ➔ Stripe Webhook Pipeline Specification Webhook Specification, Headers & Security

Technical Integration Summary

Technical guide for receiving and processing automated Make.com ➔ Stripe Webhook Pipeline Specification event notifications. Follow these security guidelines to prevent unauthorized webhook calls.

Supported Events: charge.succeeded payment_intent.created invoice.payment_failed customer.subscription.deleted

Authentication & Request Headers

Security validation specs for Make.com ➔ Stripe Webhook Pipeline Specification endpoints:

X-Make.com➔StripeWebhookPipelineSpecification-Signature: t=1789764051,v1=270ef7cb3911eb890fcd1c4b

Signature Verification Implementations

Node.js (Express)

const crypto = require('crypto');
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const isValid = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));

Python (Flask / FastAPI)

import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
is_valid = hmac.compare_digest(expected, incoming_sig)

Sample Event Payload (charge.succeeded)

{
  "id": "evt_make-to-stripe.html_52743",
  "event": "charge.succeeded",
  "created_at": 1789764051,
  "data": {
    "resource_id": "res_165",
    "status": "active"
  }
}

cURL Request Simulation

curl -X POST https://your-domain.com/webhook/make-to-stripe.html \
  -H "Content-Type: application/json" \
  -H "X-Make.com➔StripeWebhookPipelineSpecification-Signature: t=1789764051,v1=270ef7cb3911eb890fcd1c4b" \
  -d '{"id": "evt_make-to-stripe.html_52743", "event": "charge.succeeded", "created_at": 1789764051, "data": {"resource_id": "res_165", "status": "active"}}'

HTTP Response Rules

Status Code	Status Meaning	Integration Action
`200 OK`	Success	Event payload validated and queued.
`400 Bad Request`	Malformed Payload	Check payload structure and JSON formatting.
`401 Unauthorized`	Signature Mismatch	Verify secret key and digest computation.
`500 Error`	Server Error	Triggers provider automated retry backoff.

Security Best Practices for Make.com ➔ Stripe Webhook Pipeline Specification

Always process incoming events asynchronously using a message queue. Never perform long-running DB queries or external API calls synchronously within the HTTP response handler.

Frequently Asked Questions

Why does signature validation fail on Express/Flask?

Your framework might be auto-parsing JSON. HMAC generation requires the exact raw byte buffer of the request body before JSON middleware alters keys or spacing.

How does Make.com ➔ Stripe Webhook Pipeline Specification handle automatic delivery retries?

Failed deliveries (non-2xx responses) trigger an exponential backoff retry schedule over a period ranging from 24 to 72 hours.

Should I restrict incoming IP addresses for Make.com ➔ Stripe Webhook Pipeline Specification?

While signature verification is primary, restricting traffic to published origin IP ranges adds a robust layer of perimeter security.