Sandbox demo. No real money moves.

Try the complete flow

Testing guide

From fan wishes to a batch result in about five minutes. You play both the maker and a fan.

Before you start

On the hosted build, start below: no installation, account, or credentials are needed to browse. Only the payment step needs a PayPal sandbox personal account.

The free instance sleeps after 15 minutes without traffic. The first request after idle can take about a minute.

This product only talks to the PayPal sandbox. No real money moves.

Use the sandbox buyer account given in the submission's testing instructions, or your own PayPal sandbox personal account. Keep its details in the PayPal window.

Follow these steps

  1. Start a demo. The button below creates a separate sample workspace and opens the maker home. Keep that tab open throughout the test.
  2. Look at the wishes. On the maker home, open Wishes to read the sample fan requests. You can also open the fan wish page and leave a request in your own words. A wish is not an order and nothing is charged. When an offer is open, a wish left after the stored analysis receives a separate offer-reading attempt; its status can remain pending. The reply drafts and proposal counts still refer to the stored analysis until you run analysis again.
  3. Read the stored analysis and evidence. Open Proposal to review the stored seed run. A live re-run is optional. Read the proposed product, quoted wishes, and the groups showing which requests it can serve. AI groups the wishes; the maker chooses the offer.
  4. Confirm the offer. Use the proposal to open Offer. Review the product, price, delivery terms, minimum batch, capacity, and campaign window. Select Check this price to review which wishes fit your price. Keep the demo minimum at 3 units and choose 15 minutes. Resolve each maker question, confirm that you can produce and deliver the offer, and publish it.
  5. Open the fan offer page. From the maker workspace, open the fan offer link in a new tab. Review the exact offer and payment terms while keeping the maker tab available.
  6. Authorize with PayPal: choose quantity 3. Set the quantity to 3 and review the updated total, then use the PayPal button and approve with a sandbox personal account. One approval covers the demo minimum. Return to the fan page and check that the authorization is recorded. A hold is not a completed payment; capture can still fail.
  7. Confirm production as the maker. Return to the maker tab and open Campaign. Authorized units update automatically. When the minimum is met, select Confirm production, review the capture summary, select the acknowledgment checkbox, then select Confirm production again to request payment capture.
  8. See the result. Open the maker's result page and inspect the payment states and timeline, including PayPal IDs. The batch is funded only when enough payments complete. If a payment fails or is pending, read its status instead of treating the authorization as paid.
  9. Check against PayPal. From the result, open Check payment books, then select Check against PayPal to compare the recorded pledges with sandbox resources. Review each match or attention status; a recorded payment state alone is not a provider comparison.
  10. Verify the decision record. Open decision record, then Verify this record. Review whether the stored chain is intact. Select Simulation - tampered copy to see a changed copy fail verification; the simulation changes no real record or payment state. Verification checks stored contents, not whether an interpretation was correct.
  11. Trace the fan's pledge. Open the pledge trace from the decision record, or return to the fan pledge page and select Trace my pledge. Review the wish association, offer reading, and payment checkpoints. An unavailable wish association stays unknown; it is not inferred from the pledge.
  12. Read the public batch explanation. On the fan offer or result page, select Batch explanation in the guide bar to open How this batch was chosen. Review the proposal evidence and the maker's published offer.
  13. Try the reliability drills. Open Reliability drills / simulated examples from the campaign overview, or Synthetic reliability drills from the result. These labeled simulations show failure paths without changing a real campaign or calling PayPal.

Three counts, three meanings

Stated interest counts wishes classified as requests. Authorized holds count offer units with payment authorization. Paid counts units whose payments have completed. Wishes are never added to authorized or paid units, and holds are never treated as completed payments.

Optional: try cancellation

Start a fresh demo from this guide and repeat the steps through publishing and authorizing a pledge. This takes a second PayPal approval. Before confirming production, return to the maker's Campaign page and cancel the campaign. Check the fan pledge status and the maker timeline for the hold-release outcome. PayPal releases the hold; when the amount reappears depends on PayPal and your bank or card.

Local-run alternative

You can also run the app locally by following the running guide, then follow the same steps here. Local payments require sandbox REST application credentials on the server as well as a sandbox personal buyer account; live reanalysis needs a model key.