A working checkout still needs an HTTPS renewal owner

Current HTTPS is a condition, not a handoff record

The WooCommerce Stripe express-checkout documentation requires a valid SSL certificate for the domain and HTTPS across the entire site. It also describes additional method-specific domain and security requirements. Those requirements explain why the merchant should keep HTTPS responsibility visible after delivery. They do not say which company renews a particular store's certificate.

A currently usable checkout answers an observation about the site now. It does not answer who receives a renewal notice, which service manages the certificate or who is responsible if renewal needs attention. The task here is to establish those operating dependencies, not to diagnose a missing wallet button or change security settings.

Connect the exact hostname to the real service

List the store hostname buyers use and any separate checkout hostname that is actually part of the site's current journey. For each, locate the corresponding certificate-management record through an authorized service account or a configuration record supplied by the responsible team. Keep the public hostname in the worksheet; do not copy private checkout-session links.

Record both the certificate information you can observe and the service the team identifies as managing it. Do not assign renewal to a hosting company merely because it hosts the website, or to the agency merely because it built checkout. Require a record connecting the hostname to that service and an acknowledgment of the responsibility being handed over.

If the hostname is documented but the managing service is unknown, name that exact gap. If the service is identified but the merchant cannot reach an authorized contact, record the contact dependency separately. Combining these into a single 'SSL complete' checkbox would hide what remains to be established.

Separate the certificate date from the renewal commitment

Copy a known certificate expiry date or a real renewal event only with its source and observation date. If a service record shows a scheduled renewal, describe it as the service's stated schedule. If a completed event is recorded, describe that event. A date copied without identifying the certificate or hostname cannot establish coverage for this checkout.

Ask the responsible team to identify the renewal arrangement for the actual service. Where automation is claimed, record the service evidence and who is responsible for responding when it reports a problem. Do not mark renewal as automatic based solely on a working HTTPS page or a past successful renewal. This worksheet supplies no universal renewal interval or provider-specific instructions.

During a vendor change, compare the recorded arrangement with the agreed scope after handoff. Determine whether the same team continues to own it, whether another team has accepted it or whether responsibility remains undecided. A proposed new owner belongs in the open questions until that team acknowledges the hostname and work.

Close the responsibility gap without editing the setup

A usable HTTPS dependency record identifies the hostname, managing service, responsible team, available renewal evidence and a route for raising a problem. Add the merchant contact who can coordinate action and any genuine deadline already documented. If a role or record is missing, give the follow-up a named owner rather than treating the current checkout as proof that the dependency is covered.

Do not change certificates, DNS, HTTPS settings or validation files merely to complete this inventory. It is enough to document the current arrangement and identify who can evaluate an actual change. An existing warning or expired-certificate record belongs with the responsible service team as a concrete finding; this page does not promise a restoration time.

For a scoped Prism checkout consultation, provide the public website, research-only products and a concise explanation of the unresolved dependency. Prism's published support is storefront review, processing preparation and help with provider website questions. Confirm any requested certificate-related assistance, responsibilities, fees and terms before work. The merchant decides which changes to make, and the provider separately decides processing eligibility. The inquiry receives email follow-up and is not a booking, purchase or processing application.

HTTPS dependency record

Complete this for each actual store or checkout hostname. Keep observed validity, documented renewal behavior and assigned responsibility separate. An unknown service or unacknowledged owner remains an open handoff item even when the page currently loads.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.