# Tebex Webhooks

## When to Use This Skill

* Setting up Tebex webhook handlers
* Debugging Tebex `X-Signature` verification failures
* Completing the `validation.webhook` handshake so an endpoint activates
* Handling payment, dispute, and recurring-payment events

## Verification (core)

Tebex has no SDK. Verify the hex `X-Signature` header manually. The signature
is two-step: SHA-256 hash the raw request body, then HMAC-SHA256 that
hex hash using your webhook secret as the key. Do not `JSON.parse` before
verifying — a re-serialized body produces a different hash.

Node:

```javascript
const crypto = require('crypto');

function verifyTebexSignature(rawBody, signatureHeader, secret) {
  const bodyHash = crypto.createHash('sha256').update(rawBody).digest('hex');
  const expected = crypto.createHmac('sha256', secret).update(bodyHash).digest('hex');
  const received = Buffer.from(signatureHeader || '');
  const expectedBuf = Buffer.from(expected);
  return received.length === expectedBuf.length &&
    crypto.timingSafeEqual(received, expectedBuf);
}

```

Python:

```python
import hashlib, hmac

def verify_tebex_signature(raw_body: bytes, signature: str, secret: str) -> bool:
    body_hash = hashlib.sha256(raw_body).hexdigest()
    expected = hmac.new(secret.encode(), body_hash.encode(), hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, signature or "")

```

Validation handshake: On setup Tebex sends a `validation.webhook` ping.
After verifying the signature, respond `200` with `{"id": "<payload.id>"}`
echoing the received `id`, or the endpoint never activates.

> For complete handlers with route wiring, event dispatch, and tests, see:
> 
> * [examples/express/](https://github.com/hookdeck/webhook-skills/tree/main/skills/tebex-webhooks/examples/express/)
> * [examples/nextjs/](https://github.com/hookdeck/webhook-skills/tree/main/skills/tebex-webhooks/examples/nextjs/)
> * [examples/fastapi/](https://github.com/hookdeck/webhook-skills/tree/main/skills/tebex-webhooks/examples/fastapi/)

## Common Event Types

| Event | Description |
| --- | --- |
| `validation.webhook` | Setup ping — echo the `id` back with a 200 to activate the endpoint |
| `payment.completed` | A payment completed successfully |
| `payment.declined` | A payment was declined |
| `payment.refunded` | A payment was refunded |
| `payment.dispute.opened` | A chargeback/dispute was opened |
| `payment.dispute.won` | A dispute was resolved in your favor |
| `payment.dispute.lost` | A dispute was resolved against you |
| `payment.dispute.closed` | A dispute was closed |
| `recurring-payment.started` | A subscription began |
| `recurring-payment.renewed` | A subscription renewed |
| `recurring-payment.ended` | A subscription ended |
| `recurring-payment.cancellation.requested` | A subscription cancellation was requested |
| `recurring-payment.cancellation.aborted` | A pending cancellation was aborted |

> For the full event reference, see [Tebex Webhooks](https://docs.tebex.io/developers/webhooks/overview).

## Payload Structure

Every webhook has the same envelope: `id` (unique webhook ID), `type` (event
name), `date` (ISO timestamp), and `subject` (event-specific data).

## Environment Variables

```bash
TEBEX_WEBHOOK_SECRET=your_webhook_secret_here   # Creator Panel > Developers > Webhooks > Endpoints

```

## Source IP Allowlist

Tebex sends webhooks only from `18.209.80.3` and `54.87.231.232`. The docs
suggest returning `404` to requests from any other IP. See
[references/verification.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/tebex-webhooks/references/verification.md) for an example.

## Local Development

```bash
# Start tunnel (no account needed)
npx hookdeck-cli listen 3000 tebex --path /webhooks/tebex

```

## Reference Materials

* [references/overview.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/tebex-webhooks/references/overview.md) - Tebex webhook concepts and events
* [references/setup.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/tebex-webhooks/references/setup.md) - Creator Panel configuration
* [references/verification.md](https://github.com/hookdeck/webhook-skills/blob/main/skills/tebex-webhooks/references/verification.md) - Signature verification details