Sync
Your plan should survive a reinstall.
Klyaso syncs billing truth from Paddle into a mirrored subscription database, then exposes a clean /me snapshot to the extension — so entitlements stay coherent.
What it does
- Refresh subscription state from Klyaso’s mirrored billing database.
- Restore purchases by syncing live Paddle subscriptions into that mirror.
- Drive feature gates from hasPaidAccess — not guesswork.
- Invalidate caches after checkout, restore, and account changes.
Why it matters
Nothing erodes trust faster than paying for Influencer and seeing free locks after a browser reset. Sync is the quiet infrastructure that makes premium feel real.
Common workflow
How creators use it
Step 01
Checkout completes in Paddle
Webhooks update the mirrored customer and subscription rows.
Step 02
Extension reads GET /api/paddle/me
The client caches a safe payload — plan, status, trial, renewal, hasPaidAccess — without Paddle IDs.
Step 03
Restore when local state is stale
POST /api/paddle/restore pulls from Paddle, upserts the mirror, and returns the same /me shape.
Where Instagram falls short
Klyaso is not positioned against other marketing suites. It is positioned against the friction Instagram leaves on the desk of people who create for a living.
- Instagram cannot sync Klyaso entitlements.
- Local-only extension storage breaks across machines without a server mirror.
- Client-trusted customer IDs are a security footgun — sync must be server-resolved.
How Klyaso solves it
- Webhook-backed mirror of customers and subscriptions.
- Canonical /api/paddle/me for UI and gates.
- Idempotent restore that never duplicates subscription rows.
- Short-lived client cache with deliberate invalidation points.
Benefits you will feel
- Reliable premium unlocks.
- Safer identity boundaries.
- Predictable behavior after reinstall.
Inside Klyaso
Sync
Entitlements refreshed from mirrored billing state.
FAQ
Why isn’t my plan updating instantly after checkout?
Checkout confirmation syncs the transaction and subscription when Paddle is ready; Restore Purchases can force a mirror refresh if webhooks lag.
Does sync expose my Paddle IDs to the extension?
The /me payload intentionally omits Paddle and database IDs. Customer IDs are resolved server-side.
Try Sync inside Klyaso
Install the extension, open Instagram.com, and keep this workflow beside the feed — where the work already happens.
Install Klyaso