Skip to main content

Setting Up and Troubleshooting Webhooks

I
Written by Inverite Marketing
Updated over 2 weeks ago

Inverite uses webhooks to notify your platform in real time when an IBV session is completed. This allows your system to act on verification results without polling the API.

How to Set Up a Webhook

• Step 1: Your team provisions and hosts the webhook endpoint. Inverite does not host endpoints on your behalf.

• Step 2: Send the endpoint URL to Merchant Support and we will configure it on your account.

• Step 3: Once configured, Inverite will POST the IBV result payload to your endpoint when a session completes.

Testing Webhooks During Development

For local development, use a tunneling tool such as ngrok to expose your local server to the internet. This allows Inverite to deliver webhook payloads to your development environment without requiring a public URL.

You can also use webhook.site to inspect payloads and confirm the structure before building your handler.

Troubleshooting Missing or Failed Webhooks

Not receiving webhooks at all

• Confirm your endpoint URL is publicly accessible (not localhost without a tunnel)

• Verify the URL was sent to and confirmed by Merchant Support

• Check your server logs for incoming POST requests being blocked by a firewall or WAF

Webhook delivering but your handler is failing

• Confirm your endpoint returns a 200 OK response promptly — Inverite may retry on non-200 responses

• Review the incoming payload structure against the Inverite API documentation

• Check for timeout issues if your handler performs heavy processing synchronously

Intermittent failures

• Transient network issues can occasionally cause delivery failures. Inverite will retry failed deliveries.

• If you see a pattern of failures, open a Merchant Support ticket with the session dates and times so we can investigate delivery logs.

Tip: Always include the Inverite request ID in your support ticket when reporting webhook issues — this is the fastest way for our team to locate the relevant delivery logs.

Did this answer your question?