Event categories
Pocketsflow webhooks are organized into the following categories:Order Events
Track purchases, refunds, and order updates
Subscription Events
Monitor recurring billing and subscription lifecycle
Customer Events
Sync customer creation and updates
Product Events
Track product catalog changes
Review Events
Receive notifications for new product reviews
Payment Events
Monitor payment processing and failures
Invoice Events
Track subscription billing and invoices
Identity Events
Monitor KYC verification status
Order Events
order.completed
Fired when a customer successfully completes a purchase.
Use cases:
- Grant access to digital products or courses
- Send welcome emails
- Sync to CRM or internal database
- Trigger fulfillment workflows
order.refunded
Fired when an order is fully or partially refunded.
Use cases:
- Revoke product access
- Update analytics dashboards
- Send refund confirmation emails
- Alert finance team
Subscription Events
customer.subscription.created
Fired when a customer starts a new subscription.
Use cases:
- Grant subscription access
- Send welcome email
- Create member account
- Sync to membership platform
customer.subscription.updated
Fired when subscription details change (plan upgrade, pause, etc.).
Use cases:
- Update user permissions
- Sync plan changes
- Send confirmation emails
customer.subscription.created with updated fields.
customer.subscription.deleted
Fired when a subscription is canceled (immediately or at period end).
Use cases:
- Revoke subscription access
- Send cancellation confirmation
- Trigger win-back campaigns
- Update member status
customer.subscription.paused
Fired when a subscription is paused.
Payload: Similar to subscription.updated with status: "paused".
customer.subscription.resumed
Fired when a paused subscription is resumed.
Payload: Similar to subscription.updated with status: "active".
customer.subscription.trial_will_end
Fired 3 days before trial period ends.
Use cases:
- Send trial ending reminder
- Prompt for payment method
- Highlight premium features
Invoice Events
invoice.created
Fired when a new subscription invoice is generated.
Payload:
invoice.payment_succeeded
Fired when a recurring subscription payment succeeds.
Use cases:
- Extend subscription access
- Send receipt email
- Update billing records
- Track MRR
invoice.payment_failed
Fired when a recurring payment fails.
Use cases:
- Send payment failure notification
- Request payment method update
- Pause subscription access
- Track churn risk
invoice.upcoming
Fired 7 days before next invoice is due.
Use cases:
- Send payment reminder
- Preview upcoming charges
- Allow plan changes
Payment Events
payment_intent.succeeded
Fired when an initial subscription payment succeeds.
Payload:
payment_intent.payment_failed
Fired when an initial payment fails.
Payload:
Customer Events
customer.created
Fired when a new customer is created in your account.
Use cases:
- Add to CRM
- Send welcome series
- Create user account
- Track customer acquisition
Product Events
product.created
Fired when you create a new product.
Use cases:
- Sync to external catalog
- Update inventory systems
- Notify affiliates
product.updated
Fired when product details are modified.
Payload: Same structure as product.created.
product.deleted
Fired when a product is deleted.
Payload:
Review Events
review.created
Fired when a customer leaves a product review.
Use cases:
- Send thank you email
- Display on marketing pages
- Analyze product sentiment
- Alert team of low ratings
Identity Verification Events
identity.verification_session.verified
Fired when KYC verification is completed successfully.
Use cases:
- Approve seller account
- Enable payouts
- Send confirmation email
identity.verification_session.processing
Fired when verification is being reviewed.
Payload: Similar structure with status: "processing".
identity.verification_session.requires_input
Fired when additional information is needed.
Payload:
Common Payload Fields
All webhook events include these standard fields:| Field | Type | Description |
|---|---|---|
webhookId | string | ID of the webhook configuration |
event | string | Event type (e.g., “order.completed”) |
timestamp | number | Unix timestamp (milliseconds) |
testMode | boolean | Whether this is a test event |
livemode | boolean | Opposite of testMode |
X-Pocketsflow-Signature: HMAC SHA256 signature for verificationX-Pocketsflow-Event: Event typeX-Pocketsflow-Timestamp: Event timestamp
Testing Event Payloads
Using the Dashboard
- Go to Settings → Developers → Webhooks
- Select your webhook
- Click Send Test Event
- Choose an event type
- Review the sent payload
Logging Webhooks Locally
Using Webhook Testing Tools
- Webhook.site - Inspect webhook payloads
- RequestBin - Collect and debug webhooks
- ngrok - Test locally with HTTPS
Event-Driven Architecture Examples
Grant Course Access
Manage Subscription Access
Sync to CRM
Next Steps
Authentication & Security
Learn how to verify webhook signatures
Code Examples
See complete webhook implementations
Consuming Webhooks
Best practices for handling webhooks
Webhook Overview
Back to webhooks overview