Sync Stripe entities into PostgreSQL via managed webhooks and backfill.
npx skills add https://github.com/KhaledMKhaled/FodaStore --skill stripe-khaledmkhaled
Please help me install this Agent Skill. Skill: stripe Source: https://github.com/KhaledMKhaled/FodaStore/tree/main/.local/skills/stripe Command: npx skills add https://github.com/KhaledMKhaled/FodaStore --skill stripe-khaledmkhaled
This Skill prevents broken Stripe payment setups by guiding a correct end-to-end integration pattern: initializing the Stripe sync layer, configuring the webhook safely, and wiring read/write code paths so Stripe remains the source of truth for products, prices, and related entities.
Use the stripe skill to set up the managed Stripe migrations, create the webhook handler and route under /api/stripe/webhook before express.json(), then implement storage queries that read from the synced stripe.* tables while creating products and prices via Stripe API scripts.
High-intent search queries and answers about installing and using this skill.
To sync Stripe data with PostgreSQL, run stripe-replit-sync migrations before initialization to create the stripe schema, then use backfill and managed webhooks to keep products, prices, and customers updated in your Node Express backend.
Stripe webhook signature verification fails if the route is registered after express.json(). You must register the raw-buffer webhook route before body parsing to ensure the payload remains intact for verification.
The correct initialization order requires running stripe-replit-sync migrations before calling getStripeSync, and registering the raw-buffer webhook route before express.json to process payloads correctly.
No, you should not create duplicate product tables. Stripe remains the source of truth; query the synced stripe.* tables for products and prices, and store only Stripe IDs in your application tables.
You can create checkout sessions by using common endpoint scaffolding that reads product and price data from your synced stripe.* tables, allowing you to build typical flows like listing products and handling user subscriptions.
Yes, this pattern is designed for Replit Express backends, providing CRUD-like workflows for subscriptions and checkout sessions while ensuring safe defaults and reliable webhook processing.
soq123Integrate Stripe payments and sync entities with PostgreSQL webhooks.
naopensedoit2-designSet up Stripe migrations, managed webhooks, and PostgreSQL sync workflows.
Celia-12Integrate Stripe payments and sync entities into a PostgreSQL stripe schema.
Exocore-OrganizationIntegrate Stripe payments into mobile apps and sync data to PostgreSQL.
