Testing Subscriptions with Stripe Test Clocks

Overview

Stripe Test Clocks can help simulate subscription renewals and billing changes in Test Mode. They are useful when you want to confirm that PayPress receives renewal webhook events and creates renewal orders.

Requirements

• Stripe Test Mode.
• Stripe Test Clock configured in Stripe.
• Test Clock customer in Stripe.
• Subscription created for that Test Clock customer.
• Webhooks configured in PayPress.

Steps

1. Create a Test Clock in Stripe.
2. Create or use a customer attached to that Test Clock.
3. Create a subscription for the Test Clock customer.
4. Ensure ownership metadata is present if creating the subscription outside the normal PayPress checkout flow.
5. Advance the Test Clock in Stripe.
6. Review Stripe invoice events.
7. Check PayPress Orders for renewal orders.
8. Check PayPress Subscriptions for status updates.

Expected Result

Successful renewal invoices should create new local PayPress orders when the events pass ownership validation. Failed invoice attempts should appear according to Stripe event behavior and PayPress webhook processing.

Important Notes

If you create subscriptions manually in Stripe instead of through PayPress checkout, ownership metadata may be required for PayPress to accept the webhook as local. Stripe test cards behave differently depending on the specific card number and scenario.

Troubleshooting

If PayPress ignores a Test Clock event as foreign, confirm ownership metadata. If a renewal succeeds instead of failing, confirm the test card is intended to fail recurring payments in the scenario you are testing. If no renewal order appears, inspect invoice webhook events.

Related Articles

• Subscription Renewals
• Failed Renewal Payments
• Webhook Setup
• Testing Payments