Stripe Webhook Configuration

Once you've connected Stripe in LIVE and TEST modes, you'll see the option to configure Webhook Settings.

After a successful Stripe Connect OAuth for a mode, Payment Page provisions its endpoint synchronously and saves the returned signing secret. For an existing Payment Page 1.5.2 connection, a bounded background task can update the event list on the exact endpoint owned by Payment Page. That upgrade does not delete the endpoint, change its API version, or rotate its signing secret. Payment Page does not alter a manually managed endpoint, even when it uses the same callback URL.

Payment Page 1.5.3 requires this exact event list:

• payment_intent.succeeded
• payment_intent.payment_failed
• payment_intent.processing
• payment_intent.canceled
• setup_intent.succeeded
• setup_intent.setup_failed
• setup_intent.canceled
• invoice.paid
• invoice.payment_failed
• customer.subscription.created
• customer.subscription.updated
• customer.subscription.deleted

The plugin validates Payment Page metadata, the site domain, test/live mode, amount, currency, and the exact stored Stripe object lineage before accepting an event. It records one-time payment status, initial subscription settlement, paid renewal invoices, failed invoices, SetupIntent outcomes, and subscription status changes through dedicated code paths. Duplicate event delivery and downstream success effects use durable per-event guards.

Stripe checkout remains paused for a mode until Payment Page has a signing secret and records the 1.5.3 event contract as ready. If the automatic upgrade cannot safely identify an endpoint it owns, the admin notice directs you to complete the manual configuration below.

Go to your Stripe Webhooks Settings, enter the mode-specific Webhook URL shown by Payment Page, and select all 12 events listed above. Do not select an approximate subset: one-time status, payment-method setup, initial subscription settlement, renewals, failed invoices, and subscription status changes use different events.

After you create the endpoint, reveal its signing secret in Stripe. Stripe's Dashboard labels and layout can change; use the endpoint details for the exact test or live endpoint you just created.

Paste the Signing Secret into the plugin Webhook Settings. The screenshot above uses a fixed redaction value; it does not expose a real signing secret.

Be sure to click Save Settings, and follow the exact same process for both LIVE and TEST modes. Saving a non-empty secret marks a manual configuration as complete, so verify the endpoint's URL, mode, and complete event list before saving.