Installation UUID Issues

PayPress uses an installation UUID to identify which WordPress installation created a Stripe Checkout Session.

Overview

PayPress uses an installation UUID to identify which WordPress installation created a Stripe Checkout Session.

Symptoms

  • Foreign Event Ignored appears unexpectedly.
  • Diagnostics mention stored home URL changed.
  • WP-CLI, staging, localhost, or IP-based requests show different URLs.
  • A cloned site shares Stripe credentials with production.

Likely Causes

  • Multiple installations use the same Stripe account.
  • Site URL varies by browser, CLI, proxy, or server context.
  • A site was cloned or restored.
  • The installation UUID option was deleted during full uninstall/data removal.
  • Old Stripe objects do not contain installation UUID metadata.

Resolution Steps

  1. Check PayPress Diagnostics for the local installation UUID.
  2. Confirm the UUID is stable across browser and WP-CLI contexts.
  3. Review stored home URL diagnostics.
  4. Confirm the payment was created by this PayPress installation.
  5. If the site was cloned, treat ownership carefully before accepting payments.
  6. Do not manually change the UUID unless you understand the ownership impact.

Expected Result

A valid existing UUID should remain stable. URL changes should create warnings, not silently rotate identity.

Additional Notes

PayPress should not regenerate a valid UUID simply because home_url() changes. Stored Home URL Changed diagnostics are warnings about environment variation.

Related Articles