Launch Console.

Readiness, without guesswork.

Implementation, service connection and live testing are separate steps. Paid checkout stays disabled until the required configuration and owner approval are in place.

This checks account access only. It does not create a checkout, charge a card, upload a film or prove end-to-end playback.

Connect the services

1. Create a Stripe account. Start in its test environment. Create a monthly recurring price using your chosen amount and currency. Enable the customer portal with invoices, payment updates and cancellation. Add the webhook endpoint https://kinoflix.com/api/webhooks/stripe for checkout.session.completed and customer.subscription.created / updated / deleted.
2. Create a Cloudflare Stream account. Add an API token scoped to Stream for that account. Retain the account ID and Stream customer code. Upload a test video, enable signed URLs and add captions.
3. Configure runtime values securely. Add STRIPE_SECRET_KEY, STRIPE_PRICE_ID, STRIPE_WEBHOOK_SECRET, BILLING_MODE=test, CF_ACCOUNT_ID, CF_STREAM_API_TOKEN and CF_STREAM_CUSTOMER_CODE through the Site’s environment settings. Keys and signing secrets must be marked secret. Deploy after changing runtime values. Don’t paste keys into page fields or chat.
4. Run the launch tests below. Add a rights-cleared test film in Studio. Confirm publication, playback, subtitles, membership enforcement, payment failures, cancellation and support handling.
5. Approve the commercial launch separately. Confirm business identity, launch countries, rights, taxes, recurring-price disclosure, privacy notice and subscription terms with appropriate professional review. Live mode requires matching live credentials plus BILLING_MODE=live, LEGAL_READY=yes and PAID_LAUNCH_APPROVED=yes. These flags are not a substitute for completing the work.

Test records

Record what you tested, the device or environment and the result. These notes document your work; the site does not independently verify them.

Backups & recovery

Download a dated snapshot of film metadata and rights records. The catalog export contains no member data. The private database snapshot contains all eight application tables, with a limit of 1,000 rows per table; exports over that limit are refused rather than silently truncated. Neither export is a completed restore drill. Keep it in a secure location.

The private snapshot includes member and support records and billing identifiers. Store it securely. It contains no provider API keys or payment-card data. Managed database recovery must be verified with the hosting provider. Don’t restore production data without first checking the current state and the effect on newer records.

Support inbox

Requests are stored here. Replies are handled manually through email. No automatic response has been promised.