Webhook Endpoint Setup Integration Block for React

Everything. The secret is checked only for its whsec_ shape, never stored, never sent and cleared on finish; the test event only changes the status line, and the endpoint address is on a reserved example domain. Wire your own endpoint, signature check and test where the demo changes state.

Yes. Each webhook endpoint you add in the Stripe Dashboard has its own signing secret that starts with whsec_, which is used to verify the signature header Stripe sends with every event. The four event names (invoice.payment_failed, invoice.paid, customer.subscription.deleted, charge.dispute.created) are real event types.

The schedule starts on a failed payment and stops when the invoice is paid, so without them the product cannot work. Pressing a locked row leaves it on and says why in the status line.

Each band is a list item whose heading starts with "Done:" or "To do:" for screen readers. Every field has a visible label, the checkboxes are named by their event, the unavailable buttons are marked as such and explain themselves in the status line, which is a polite live region present from load.

A real test needs a secret to sign against. Until the secret has the right shape the button is marked unavailable; pressing it says what is missing. Changing the secret or the events afterwards clears the test, so Finish setup waits for a fresh one.

On a phone each band stacks its control under its step, and the foot band puts the buttons under the status line. In a right-to-left layout the bands mirror; the endpoint, the secret and the event names keep their own direction.