Define the payment spec

Lock what is being sold, prices, and payment states before touching Stripe.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Define the payment spec for this app. Specify: what is being sold (one-time purchase or subscription plans with exact prices and currency), the payment states we must track (pending, paid, failed, canceled), what a user gets when paid, and where payment records are stored. State explicitly that all amounts live on the server and that payment success is only confirmed server-side. Do not implement yet.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A concrete payment spec with products, prices, states, and storage.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Products and exact prices are listedOne-time vs subscription is decidedPayment states are enumeratedServer-side confirmation is stated as a rule

Do not continue if…

! A 'Pay' button that redirects to a success page without ever calling Stripe
! Payment status set from the client success redirect instead of server verification
! Secret key exposed in frontend code
! No handling of canceled or failed payments

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The payment spec is vague. Rewrite it with exact products, prices, currency, payment states, and the rule that only the server confirms payment success.