← Spec Hub | Category: Payments & Billing
Technical guide for receiving and processing automated Stripe ➔ Vectorizer.AI 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
Security validation specs for Stripe ➔ Vectorizer.AI Webhook Pipeline Specification endpoints:
X-Stripe➔Vectorizer.AIWebhookPipelineSpecification-Signature: t=1789764056,v1=fbd2ca8ca743870a73567cf3
const crypto = require('crypto');
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const isValid = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));
import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
is_valid = hmac.compare_digest(expected, incoming_sig)
{
"id": "evt_stripe-to-vectorizer.html_74206",
"event": "charge.succeeded",
"created_at": 1789764056,
"data": {
"resource_id": "res_383",
"status": "active"
}
}
curl -X POST https://your-domain.com/webhook/stripe-to-vectorizer.html \
-H "Content-Type: application/json" \
-H "X-Stripe➔Vectorizer.AIWebhookPipelineSpecification-Signature: t=1789764056,v1=fbd2ca8ca743870a73567cf3" \
-d '{"id": "evt_stripe-to-vectorizer.html_74206", "event": "charge.succeeded", "created_at": 1789764056, "data": {"resource_id": "res_383", "status": "active"}}'
| 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. |
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.
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.
Your endpoint must return an HTTP 2xx response within 2000ms. Offload heavy processing (email, DB writes) to an asynchronous task queue.
A 429 status indicates your endpoint is being rate limited. Implement dynamic throttling or increase consumer worker threads in your queue worker.