Who can do what
Organization owners and admins don’t get webhook access through their organization role. They need a project role like anyone else. Members without write access see the panel read-only.
Owners and admins also receive the emails Trustware sends when a webhook event fails every attempt or the URL is disabled.
Register your webhook URL
1
Open the project
Go to the Projects tab and select the project. The Webhooks panel sits below the project’s API keys.
2
Enter the URL
Enter your endpoint in Webhook URL and click Register URL. It must be a public
https URL on port 443. See webhook URL requirements for the full list. If the dashboard refuses the URL, the error says why.3
Copy the secret
The dashboard shows your signing secret, starting with
whsec_, once. Click Copy and store it in your server’s secrets. When you dismiss the alert, the secret is gone from the dashboard, and Trustware can’t show it again.4
Send a test event
Pick an event type under Send a test event and click Send test event. The attempt appears in the delivery log, which refreshes itself until the attempt finishes.
/status.
New URLs use API version v1.
Send a test event
A test event exercises your real handler without a real payment. You pick a type, and Trustware sends that type’s sample body to your URL through the normal delivery path, signed with your real secret. A test event differs from a real one in three ways:testistrue.datais sample data under the route intent ID00000000-0000-0000-0000-000000000000, which never belongs to a real route intent.sequencecomes from a separate per-project counter that only goes up, so your “already processed a newer sequence” check never discards a repeated test.
410 Gone, which disables your URL as it would for any delivery.
Make sure your production handler recognizes test: true and doesn’t act on test data, such as crediting a payment.
If you don’t have a server yet, a request inspector such as webhook.site can receive test events so you can see the exact request.
You can send up to 10 test events a minute per project. Test events are refused while the URL is disabled.
Read the delivery log
The Delivery log, last 30 days lists every delivery attempt for the project, newest first. Click a row to see:- the exact request Trustware sent: method, URL, headers (including the signature), and body
- your response status and how long it took, or the connection error
- the first 4 KiB of your response body, shown as plain text
While an attempt on the first page is still scheduled or sending, the log refreshes itself every few seconds. The panel also re-reads the URL’s state on each refresh, so if Trustware disables your URL while you’re watching, the panel shows it.
The request in the log is byte-for-byte what was signed. If your signature check fails, compare your handler’s input with it. A different body almost always means your framework parsed or re-encoded it before you verified.
Redeliver webhook events
Redelivery sends an existing webhook event again, as one extra attempt with no retries of its own. It keeps the samewebhook-id, sequence and body, and gets a fresh webhook-timestamp and signature. Your duplicate and ordering checks handle it like any other delivery.
- Redeliver this event, in an open log row, sends that one webhook event, test events included. It’s refused while that event already has an attempt scheduled or in flight.
- Redeliver undelivered sends every webhook event from the last 30 days that hasn’t been delivered and was recorded after you registered the URL. It skips test events and events that already have an attempt pending, and tells you how many it queued.
