Build the purchase journey. Verify the receipt.
Create a SaaS pricing or storefront flow with server-approved Stripe test Checkout, sign-in continuation and verified fulfillment status.
Review the prepared brief in Studio. A build starts when you send it.
Specify the complete order journey
A checkout brief needs a product selection, price source, sign-in requirement, return route and observable order status. Preserve the selected order through guest sign-in. Keep the pending state visible while payment fulfillment is reconciled. A return URL by itself does not prove payment, and a button with a success toast does not implement Checkout.
Test fulfillment before selling
Use the approved Stripe test configuration and verify receipt ownership, amount, currency and mode. Handle cancelled Checkout, delayed webhook delivery and replay without creating duplicate fulfillment. Generated-app purchases are distinct from the creator's Uvilno source unlock or studio subscription. Review live-commerce requirements before accepting customer money.
Give each screen its own job.
These are proposed interfaces for your brief. Build and verify the core workflow before adding connected companions.
Web
A catalog, cart or pricing view with a real managed test Checkout action.
Mobile
A touch-first purchase view that preserves its intent through sign-in.
Desktop
An operations workspace reading authorized order and fulfillment status.
Plan the records and their owners.
Suggested collections for this editable blueprint. Opening this page creates no database records. The plan must declare supported field types, relationships and access rules before building.
| Collection | Suggested fields | Access to decide |
|---|---|---|
products | name, description, approved_price_reference | Read only the catalog fields appropriate for customers. |
orders | owner, product_id, status, amount, currency | Customer order history is private to its owner. Fulfillment status is authoritative. |
Verify the outcome, then expand.
- Start a real Stripe test Checkout using a server-approved price.
- Preserve the selected order across guest sign-in and a cancelled Checkout.
- Keep the receipt pending until verified fulfillment is recorded.
- Verify delayed or replayed webhooks cannot create duplicate fulfillment.
From this brief to your first version.
Review the proposed workflow
Start with this editable feature brief. Confirm the primary action, target platform, actual business information and declared collection permissions before approving a plan.
Build and check the result
Review the isolated preview and execute the checks listed on this page. Begin with A catalog, cart or pricing view with a real managed test Checkout action. Resolve missing service setup and save verified progress before expanding the scope.
Connect or export when ready
Use App connections to review owned companions and shared backend changes. Unlock source when ready to export, then verify the target deployment, packaging and hosted-service configuration.
Make the starting point your own.
Questions before you build.
Can I accept live merchant payments immediately?
The documented generated-app release flow uses managed Stripe test Checkout. Live merchant operation depends on configured capabilities, onboarding and a separately verified production release.
Does a Checkout return page prove an order was paid?
No. The application should reconcile against its authorized receipt and fulfillment status. Handle delayed notifications and show pending until the recorded outcome is confirmed.