SubsieBeta
Events

Signed events for every transition.

Subscribe to a typed stream of payment and subscription events. Every delivery is signed, retried on failure and replayable — nothing happens silently.

payment.succeeded200
sig ✓ · 41ms
subscription.updated200
sig ✓ · 38ms
charge.scheduled200
sig ✓ · 45ms
payment.retrying···
attempt 2 · backoff 2h
Delivery

Reliable by default

Built so your backend always knows the truth about a subscription.

Integrity

Signed, typed payloads

Every event is signed so you can verify it came from Subsie, with a stable, typed schema you can depend on.

  • HMAC-signed deliveries
  • Typed, versioned schema
  • Idempotency keys included
EVENTS
payment.succeeded200
subscription.updated200
payout.pending200
Resilience

Automatic retries & replay

If your endpoint is down, Subsie retries with backoff and keeps a log you can inspect and replay at any time.

  • Exponential backoff
  • Delivery logs
  • One-click replay
DELIVERY
SETTLEMENTSLIVE TAIL
FAQ

Common questions

How do I verify a webhook is genuine?

Each request carries a signature header. Verify it against your endpoint secret before acting on the payload.

What gets retried?

Any non-2xx response is retried with exponential backoff over a configurable window; deliveries are logged throughout.

Can I replay past events?

Yes — every event is retained and can be re-sent to your endpoint from the dashboard or API.

Keep your backend in sync.

Create an account to register endpoints and inspect deliveries. Live events flow once settlement is enabled.