Skip to main content
Webhooks must be enabled for your environment before you can configure endpoints and receive events. While they’re disabled, you can still read event and delivery history, but you can’t change configuration, send tests or replay.
Webhooks notify your server about card-enrollment results, mandate-setup results, payment credential issuance, and the recorded outcomes of credentialed payment attempts. Sandbox and production are separate: each has its own endpoints, event history and signing secrets. See the event catalog for every event type, what it means and the data it includes.

Set up an endpoint

1

Create an endpoint

Open Webhooks in the developer dashboard. Enter a public HTTPS URL on port 443 and choose the event types you need. URLs with query parameters, credentials, IP addresses, private destinations or redirects are rejected. You can have up to five endpoints per application and environment.
2

Save the signing secret

The secret is shown once, right after creation. Store it in your server’s secret manager. Each endpoint has its own secret; your legacy account webhook secret isn’t used.
3

Verify your destination

Click Verify destination. Prava sends a signed webhook.endpoint_verification request. Verify the signature against the raw request body, then return a 2xx JSON response containing the exact challenge value you received. This is a control message, not an event you subscribe to.
4

Test and activate

Send a signed test event and confirm your receiver accepts it. Test events have test: true and synthetic IDs. Activate delivery once your receiver is ready. Changing the URL later pauses delivery until you verify again.

Roles

Dashboard access is limited to the selected application and environment.

Multi-app setups

If you manage several applications from one workspace, you can configure webhooks for each ready application from there. Webhook management needs credential generation enabled for your workspace. Your existing workspace access, environment and roles apply, and each application doesn’t need to approve it separately. To open one application’s webhooks, select Webhooks in your workspace, find the application and choose Manage webhooks. The application’s Integration view also links there.

Use one receiver for several applications

1

Create the endpoints

On Webhooks, select up to ten applications on the current page, enter the receiver URL and choose events. Prava creates a separate, paused endpoint for each application.
2

Save each signing secret

Each secret is labelled with its application. Save every one before you leave the page.
3

Verify and activate each endpoint

Open Verify and configure for each result to verify, test and activate delivery.
Each application keeps its own five-endpoint limit, signing secrets, subscriptions and delivery history. Applications you add later aren’t subscribed automatically.
With one URL for several applications, use account_id and environment from the payload only to choose which signing secret to try. Verify the signature against the unchanged raw body first, then check that the verified account and environment match the endpoint you configured before you process the event.
If a bulk setup partly fails. Each application succeeds or fails on its own, so one failure doesn’t undo the others. Retry same batch reuses each application’s original idempotency key and settings, so it doesn’t create duplicates. If a response was lost after an endpoint was created, its secret can’t be shown again; an administrator must rotate it. Secrets on screen stay visible until you hide them or leave the page. If access changes. When a user loses workspace access or an application moves out of the workspace, its webhooks can no longer be managed from the workspace. Existing endpoints stay with the application and keep running until someone authorized for that application pauses or deletes them. Not available yet: subscriptions for agent accounts, and a single combined event feed across your applications.

Use the API

Everything on this page also works through the Webhooks API with your application’s server-side secret key. Keep API keys and signing secrets out of browser code. Event catalog · Verify signatures · Delivery and recovery