Source type

Stripe Source Configuration

Stripe sources receive payment, billing, checkout, subscription, dispute, invoice, and customer events with endpoint-secret verification.

STRIPEPOST, PUT, PATCH, DELETEWebhook Signing SecretPayments
Stripe webhooks documentationStripe webhook gatewayAll source types
Stripe sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.StripeProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLSTRIPEProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Stripe configuration

Create a Stripe source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each Stripe delivery before it enters the routing workflow.

Source Type

STRIPE

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Signing Secret

Stripe source config
{
  "type": "STRIPE",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "STRIPE",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Stripe request contract

FastHook reads stripe-signature, validates the timestamp, and verifies the v1 HMAC-SHA256 signature over timestamp + '.' + raw body.

POSTPUTPATCHDELETE

Stripe headers

Preserve stripe-signature when sending Stripe test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

stripe-signature

Contains timestamp t and one or more v1 HMAC signatures.

Stripe setup

  1. Create a Stripe webhook endpoint or event destination that points to the FastHook Source URL.
  2. Copy the Stripe endpoint signing secret, usually starting with whsec_.
  3. Paste that value into FastHook's Webhook Signing Secret field.

Stripe routing hints

  • Payment, checkout, invoice, subscription, dispute, customer, and charge events usually route by the Stripe event type in the payload.
  • Use the Stripe event id as the first idempotency key before replaying billing traffic.

Continue with Stripe