Guide
Environments and Test Data
Keep product, payment, package, and customer test context aligned.
One environment per test journey
Use the intended product configuration, generated package, API origin, payment environment, and permitted test identity together. A browser success page is not proof that the matching provider event created access.
Test Connection reports product connectivity; it does not create a customer entitlement or prove a live payment. Do not use a production purchase, refund, payout, or marketing send as an incidental documentation test.
Publish deliberately
Regenerate packages after their bundled configuration changes. Inspect saved product pricing, customer delivery, and the actual exported build before publishing. Document whether your evidence is a source trace, a fixture, a test build, or an observed live workflow.
Paid products, subscriptions, and bundles must remain at least $9.99 after discounts, before tax. Free claims follow the redemption model rather than a discounted paid checkout.