Webhook Tester & Discord Integration: April 2026 Developer Update
Back to Blog
Updates 5 min read

Webhook Tester & Discord Integration: April 2026 Developer Update

WolvPay Team

Two features developers have asked for repeatedly are now live: a Webhook Tester built directly into the dashboard, and automatic Discord webhook support that reformats payloads as rich embeds without any extra configuration.

The Problem We Were Solving

Testing webhook integrations has always had unnecessary friction. To trigger a real event you needed to create an actual invoice, have a customer pay it (or simulate a payment), and then hope the event fired to your endpoint cleanly. If your endpoint was offline, misconfigured, or just not ready yet, you were stuck.

Similarly, merchants pointing their webhook URL at a Discord channel — a perfectly valid and popular use case for payment notifications — were getting raw JSON blobs that Discord renders as unformatted text. Not exactly a clean notification.

The Webhook Tester

The Webhook Tester lives at Developers › Webhook Tester. It is also accessible from a button on the Webhooks page.

From the tester you can:

  • Select any of your own active webhooks — the destination is always one you control, so the feature cannot be used to send arbitrary POST requests to external URLs
  • Choose the payment status to simulate: PAID, AWAITING_PAYMENT, CONFIRMING_PAYMENT, UNDERPAID, or EXPIRED
  • Set a custom invoice ID — useful when you want your server-side handler to match on a specific ID for testing, or leave it blank and we generate one automatically

After sending, the result panel shows you the HTTP status code, the exact payload that was sent, and the raw response body from your server. Everything the tester sends is also logged as a delivery in the Webhook Deliveries list (tagged as webhook.test), so you have a full audit trail.

Test payload structure

The tester sends a structurally identical payload to a real invoice event — same fields, same types. The only difference is the values are fixed dummy data.

{
  "invoice_id": "your-custom-id-or-auto-generated",
  "amount": "10.00",
  "description": "Test invoice from WolvPay Webhook Tester",
  "status": "PAID",
  "coin": "BTC",
  "coin_amount": "0.00015000",
  "coin_received": "0.00015000",
  "coin_address": "1A1zP1eP5QGefi2DMPTfTL5SLmv7Divf2N",
  "redirect_url": "",
  "created_at": "2026-04-28 14:00:00"
}

Rate limiting

The tester allows 10 sends per hour per account. The remaining count is shown in the card header and the button is disabled once the limit is reached. This is enough for any realistic integration session without enabling abuse.

Discord Webhook Support

Discord webhook URLs follow a specific format: https://discord.com/api/webhooks/{id}/{token}. WolvPay now detects this pattern automatically. When a webhook URL matches, the entire payload pipeline changes:

  • The JSON is not sent as raw data — it is reformatted into a Discord embed
  • The embed is colour-coded by payment status: green for PAID, blue for CONFIRMING, yellow for AWAITING, orange for UNDERPAID, red/grey for FAILED/EXPIRED
  • Each field (invoice ID, amount, coin, status, received amount) is presented as a named embed field with inline layout
  • The X-WolvPay-Signature header is omitted — Discord does not use it and it would cause the delivery to fail
  • Discord URLs are sent directly, bypassing the proxy forwarder used for standard webhooks

This applies to all three delivery paths: new invoice events, resends from the Webhook Deliveries list, and the Webhook Tester. No matter how the send is triggered, a Discord URL always receives a proper embed.

Discord embed status colours
PAID#57F287 Green
CONFIRMING#3498DB Blue
AWAITING#FEE75C Yellow
UNDERPAID#FF8910 Orange
FAILED#ED4245 Red
EXPIRED#95A5A6 Grey

How to Set It Up

  1. Get your Discord webhook URL — in any Discord channel, go to Edit Channel › Integrations › Webhooks › New Webhook, copy the URL.
  2. Create a webhook in WolvPay — go to Webhooks, click Create Webhook, paste the Discord URL. That's it. WolvPay detects it and handles the rest.
  3. Test it immediately — click Test Webhook, select your Discord webhook, choose a status, and hit Send. You'll see the embed appear in your Discord channel within seconds, and the response panel will show Discord's HTTP 204 No Content success response.

Where to Find These Features

  • Webhook Tester: Sidebar › Developers › Webhook Tester, or the “Test Webhook” button on the Webhooks page
  • Discord support: Automatic — just use a Discord URL as your webhook endpoint
  • Rate limit status: Shown live in the Webhook Tester card header
  • Test delivery logs: Webhook Deliveries table — tagged as webhook.test

Frequently Asked Questions

How many test webhooks can I send per hour?

10 per hour. The remaining count is shown in the tester card header. Enough for any integration session without enabling abuse.

Does the Webhook Tester show up in my Webhook Deliveries list?

Yes. Every test send is logged with event type webhook.test, so you can inspect the request body, HTTP status, and server response from the Webhooks page.

Do I need to configure anything for Discord webhooks to work?

No. WolvPay detects Discord webhook URLs automatically. Real events and test sends to a Discord URL are always sent as formatted embeds — no toggle, no extra setting.

Are resent deliveries also formatted as Discord embeds?

Yes. The resend function checks the URL on every attempt, so Discord formatting is applied consistently whether the send is new, a manual resend, or a test.

What payload does the Webhook Tester actually send?

A dummy invoice payload structurally identical to a real event: same fields, same types, fixed dummy values. Your server-side handler cannot tell the difference structurally — which is the point.

WolvPay
WolvPay Team

Building the future of cryptocurrency payments - 1% fees, instant withdrawals, no KYC.

Start accepting crypto payments today.

1% flat fee, instant withdrawals, zero KYC. Set up in minutes.