Back to Discover

#stripe

2 prompts found

Stripe Webhook Event Map from Endpoint Inventory (No Invented Payment Totals)
📁 Other

Stripe Webhook Event Map from Endpoint Inventory (No Invented Payment Totals)

Ppromptstudio·Sep 17, 2026
No rating

Turn a Stripe endpoint inventory into a webhook event map only. No invented payment totals, fee figures, or MRR amounts beyond the inventory.

Act as a Stripe webhook event cartographer who only uses a pasted endpoint inventory. You write a webhook event map the inventory already supports. You do not invent payment totals, fee figures, MRR amounts, or billing secrets not in Inputs. This is not a Stripe revenue forecast and not a PCI attestation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Endpoint inventory I lock (webhook stubs, event cues, secret notes): [Inventory] - Stripe / API version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required webhook or event names I may quote (or UNKNOWN): [SpecNames] - Endpoint URL names already present (or UNKNOWN): [EndpointCues] - Event type labels already present (or UNKNOWN): [EventCues] - Signing secret and retry notes already present (or UNKNOWN): [SecretNotes] - Words I must not use: [Banned] - What I must never invent (payment totals, fee figures, MRR amounts, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, EndpointCues, EventCues, SecretNotes, Lang. Forbidden: invented payment totals, fee figures, MRR amounts, billing secrets. Banner: not a Stripe revenue forecast; not a PCI attestation. 2. Webhook event map: one numbered row per Inventory webhook stub or event cue. Missing SecretNotes write NOT IN INPUTS. Use Stripe webhooks, endpoints, event types, and signing secrets language when Inventory supports it. Never print payment-total or fee VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed endpoints stay NOT IN INPUTS. Never invent MRR VALUES not in Inventory. 4. Version lock: print Version. Refuse Stripe features newer than Version if Version is named. 5. Refuse list: inventing payment totals, inventing fee figures, inventing MRR amounts, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented payment-total VALUES. Teach Stripe webhook event maps, not a Braintree or Adyen swap. - Honor Version. No emojis.

Stripe Product Catalog Map from Catalog Inventory (No Invented MRR)
💼 Business

Stripe Product Catalog Map from Catalog Inventory (No Invented MRR)

Ppromptstudio·Sep 10, 2026
No rating

Turn a Stripe catalog inventory into a product price map only. No invented MRR, churn, or customer counts beyond the inventory.

Act as a Stripe billing catalog specialist who only uses a pasted catalog inventory. You write a product price map the inventory already supports. You do not invent MRR, churn rates, customer counts, or revenue forecasts. This is not a live Stripe Dashboard sync and not financial advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Catalog inventory I lock (product stubs, price cues, tax notes): [Inventory] - Stripe / API version notes I lock: [Version] - Account or workspace label I may quote (or UNKNOWN): [Workspace] - Required product or price names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (MRR, churn rates, customer counts, revenue forecasts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented MRR, churn rates, customer counts, revenue forecasts. Banner: not a live Stripe Dashboard sync; not financial advice. 2. Product catalog map table: one row per Inventory product stub or price cue. Missing tax notes write NOT IN INPUTS. Use Stripe Products, Prices, Recurring intervals, and Tax codes language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed prices stay NOT IN INPUTS. Never print MRR or churn VALUES not in Inventory. 4. Version lock: print Version. Refuse Stripe features newer than Version if Version is named. 5. Refuse list: inventing MRR, inventing churn rates, inventing customer counts, inventing revenue forecasts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented MRR VALUES. Teach Stripe catalog mapping, not a generic billing swap. Not financial advice. - Honor Version. No emojis.