Add and test a webhook endpoint

PayerOne sends JSON POST notifications to your server when payment, order or refund activity changes. Use a publicly reachable HTTPS endpoint that can verify the PayerOne signature and safely accept repeated deliveries.

Order notifications

Supply an HTTPS `ipn_url` when creating standard checkout or an Express Wallet request. Keep customer return URLs separate: `success_url` and `fail_url` send the browser back to your application; `ipn_url` receives server notifications.

Additional dashboard endpoints

1. Open [Developer → Webhooks](https://dashboard.payerone.com/developer/webhooks).

2. Select **Add Webhook**.

3. Enter the full HTTPS URL for your receiver and save.

4. Open the endpoint action menu and select **Test Webhook**.

5. Confirm your receiver accepted a signed `webhook.test` event.

Additional dashboard webhooks require an active Starter or Pro plan. Starter allows one saved endpoint and Pro allows five. A plan or endpoint-limit message is separate from a receiver network error.

Use the action menu to **Edit** the URL or **Delete** an endpoint you no longer need. Check your website integration as well: deleting a saved dashboard webhook does not remove an `ipn_url` that your application submits on an order.

Receive safely

Verify `X-PayerOne-Signature` with your merchant Private Key against the original request bytes. Persist or queue the accepted event, then return HTTP 2xx promptly. Keep slower fulfillment work out of the request when possible.

A test event checks delivery and signature handling; it is not a customer payment. Handle `webhook.test` without creating an order, fulfilling a purchase or crediting a customer. A test may arrive more than once, so use the same duplicate protection as production events.