A successful Lemon Squeezy test checkout proves behavior in the test environment, not that the live catalogue is configured correctly. Treat test flow evidence and live configuration evidence as separate parts of a billing release.
The official test-mode guide explains that test products do not automatically transfer to live mode and that test API keys interact with test data. That separation should also be visible in the application's configuration.
Record the intended offer
Write down the customer-facing name, pricing model, currency and entitlement associated with each offer. Use the business's actual approved values rather than copying a nearby product's configuration.
Cliptude describes video generation and is associated with Lemon Squeezy in the technology catalogue. The listing does not expose its offer mappings. For this type of product, a checkout must connect to the correct allowance or access level, not simply to any purchasable provider product.
Keep provider identifiers separate from the readable offer names.
Exercise the test journey
Use the provider's designated test payment details and a controlled application account. Open checkout through the same application path the release will use.
Verify the displayed offer, complete a supported test outcome and inspect both the provider order and the application result. Then exercise a failure outcome.
Do not use real card details for test-mode experiments. Keep the provider's documented test limitations in the evidence rather than assuming every production capability is represented.
Verify webhook handling separately
A checkout can display success while the application has not processed the corresponding event. Confirm that the correct test endpoint and signing configuration receive and verify the event.
The webhook entitlement guide covers authenticity, mapping and duplicate processing.
Record the test order reference and resulting entitlement, without exposing secrets or unnecessary customer details.
Compare the live catalogue deliberately
Before release, inspect the actual live product and variant configuration through an authorized read-only review. Compare its values with the approved application offer.
Confirm that production uses live identifiers and credentials while the test environment remains isolated. Do not fix an identifier mismatch by weakening validation or accepting any provider product.
If a live offer must be created or changed, treat that as an explicit commercial configuration operation with a reviewable result.
Keep historical purchases intact
A catalogue update should not rewrite the amount or terms recorded for earlier orders. Existing entitlements may follow a grandfathering policy that differs from the current offer.
Test the release with representative historical records in an isolated copy. A new checkout path should not invalidate a customer who paid under an older valid configuration.
Finally, document which gates were demonstrated in test mode and which live facts were inspected. A real charge is a separate action requiring an authorized safe method; it is not implied by wanting a release check.
The release is ready when the intended offer, provider mapping and application fulfilment agree, and the evidence says exactly where each part was verified. That keeps a catalogue change understandable without confusing a sandbox success with production proof.
Cliptude
Stardew Valley Tracker
IcyZip