plan.sync_completed
Plan synced to PSP catalog (Stripe / PayPal / CoinPayments / Razorpay).
When this fires
The plan finishes syncing to one or more external payment-provider catalogs (Stripe, PayPal, CoinPayments, Razorpay). Fires once per active plan per sync run — a run over a project with twelve active plans emits twelve events. A plan whose providers all failed emits nothing, and inactive plans are never synced.
Required ability
project-subscription-plan:view — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "plan.sync_completed",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
"data": {
"plan_id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",
"providers": ["stripe", "paypal"],
"synced_at": "2026-05-18T10:04:58Z"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always plan.sync_completed for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string UUID | Project this event belongs to. |
data.plan_id | string UUID | Plan that was synced. |
data.providers | array of string | Slugs of providers the plan now exists on (one or more of stripe, paypal, coinpayments, razorpay — no other provider is ever synced). |
data.synced_at | ISO 8601 timestamp | When the sync run completed (slightly earlier than created_at). |
Caveats
- Partial failures retry on a follow-up run rather than emitting a separate event per provider;
data.providerslists only the providers that succeeded for that plan. - Errors during sync surface in the dashboard, not as webhook events.
Related events
plan.created— predecessor that typically triggers the first sync.plan.updated— re-sync trigger when pricing or cadence changes.- Plan events overview — back to family overview.
How is this guide?