Integration · Stripe
Verified Stripe webhooks for your AI agent.
Hooksbase verifies each Stripe webhook signature before persisting the delivery, stamps queryable provider metadata (event type, source ID, verified flag) on the event, and routes it to your AI agent — no webhook plumbing to build.
Signature verification against your Stripe webhook secret runs before Hooksbase persists the delivery. Provider metadata (event type, event ID, verified flag) gets stamped on every delivery — and becomes a first-class routing condition.
Verification + metadata
What your agent receives
// Hooksbase verifies Stripe-Signature header automatically
// Your agent receives:
{
"provider": {
"name": "stripe",
"sourceId": "evt_1O...",
"eventType": "invoice.payment_succeeded",
"verified": true
},
"payload": { /* raw Stripe event */ }
}Routable metadata fields
Match on provider fields
Once Stripeverification is enabled, these fields are available to routing rules, delivery search, and your agent's payload.
- provider.name = "stripe"
- provider.sourceId = evt_... (Stripe event ID)
- provider.eventType = e.g. "invoice.payment_succeeded"
- provider.verified = boolean
Agent recipes
Common Stripe + agent patterns
Route verified `invoice.*` events to an agent that handles dunning, retries, or subscription follow-up.
Route `radar.early_fraud_warning` events to a dedicated agent that investigates, documents, and flags the customer.
Fan-out verified successful charges to both your billing agent and an S3 archive destination for audit.
Frequently asked questions
- How do I verify Stripe webhooks with Hooksbase?
- Add the Stripe provider pack to a Hooksbase webhook and paste your Stripe webhook signing secret. Hooksbase verifies the `Stripe-Signature` header against that secret before the delivery is persisted, so your agent only ever sees events Stripe actually sent.
- Does Hooksbase check the Stripe signature before my agent sees the event?
- Yes. Hooksbase verifies the `Stripe-Signature` header before it persists the delivery, then stamps `provider.verified = true` on the event. Your agent receives only verified Stripe events with the signature already checked.
- Which Stripe event types can I route on with Hooksbase?
- Hooksbase extracts the Stripe event type into `provider.eventType` (for example `invoice.payment_succeeded` or `radar.early_fraud_warning`), so you can route on any Stripe event type as a first-class condition. The Stripe event ID is also captured as `provider.sourceId`.
- Can I send Stripe events to multiple destinations from Hooksbase?
- Yes. Hooksbase can fan a single verified Stripe event out to multiple typed destinations at once — for example your billing agent over HTTP plus an S3-compatible archive for audit — each with the full provider metadata attached.
- Can I replay a Stripe webhook delivery in Hooksbase?
- Yes. Hooksbase keeps 30-day delivery-detail retention and supports deterministic replay from the persisted dispatch snapshot, so you can re-send a verified Stripe event to your agent after a fix without asking Stripe to resend it.
Get started
Point Stripe at Hooksbase.
Configure the Stripe provider pack on a Hooksbase webhook, copy the ingest URL, paste it into your Stripe webhook settings. Every verified event lands with full provider metadata on the delivery.