Real-time events

Trigger your systems with webhooks

Deliver payment and billing events to your HTTPS endpoint with signing, retries, and delivery history in one place. Dashboard and API share the same event model.

Delivery pipeline

One line from event to endpoint

Instead of three equal cards, the connection itself is readable. Highlight moves in sequence; vertical on mobile, horizontal on desktop.

Event
Payment or subscription
hsrcpay
Signed HTTP POST
Your URL
HTTPS endpoint
Ack
2xx or queue

Why a dedicated integration layer?

Your server learns what happened instantly instead of polling. Exponential backoff on failed delivery, signature headers, and payload integrity reduce spoofing risk.

  • Unique signature and timestamp per delivery
  • 4xx vs 5xx handling; exponential backoff on transient errors
  • Replay and idempotent handling guidance for the same event
  • Latest attempts and response bodies in the Dashboard
webhook_deliveryattempt_1
POST /hooks/hsrcpay
X-Hsrcpay-Signature verification
200 processing…
retry queue waiting

Illustration only; in production endpoint URL and signing secret stay on your side.

Asymmetric layout

Wide event area, short ops notes, and a status strip. No shadows; only edge and surface separation.

Event catalog

Charges, refunds, subscriptions, and invoice lifecycle share one naming space. Filter, version, and map each environment to its own URL.

type payment_intent.succeeded

Retries

Automatic backoff intervals on transient errors.

Latency budget

SLA-friendly upper bound and dead-letter queue.

Endpoint policy

HTTPS requirement, allowlists, and header schema on one screen; changes ship with versioning.

POST https://api.yourdomain.com/hooks/hsrcpay

Verification summary

  • Signature matched
  • Retry pending
  • Permanent failure

Listen in test first, then move to production.

Follow documentation steps for handshake verification and secret rotation.