Connected systems

Automate Discord Payments with Signed Webhooks

Discfront is not only a Discord storefront layer. It can send signed outbound webhook events to your app, CRM, fulfillment system, entitlement service, or reporting stack. For delayed license-key products, your software can also call Discfront back when the customer activates a delivered key.

Back to main page Add Bot to Your Server
Workflow

How it works

Use webhooks when your Discord sales flow needs to trigger systems outside Discord, or when your own software needs to tell Discfront when delayed key access should start.

1

Event happens

A purchase, renewal, refund, dispute, access change, or key delivery event occurs.

2

Discfront emits the signal

Discfront sends the webhook event with the sale context attached.

3

Your systems react or activate access

Your systems can fulfill, notify, tag, provision, log, or send a signed activation callback for delayed key products.

Integration contract

Supported events and signed requests

Discfront signs the exact JSON body and identifies each delivery so your receiver can verify authenticity, reject stale requests, and process retries idempotently.

Outbound event coverage

LifecycleEvents
Endpoint checkwebhook.test
Purchasespurchase.paid
purchase.failed
purchase.refunded
Disputespurchase.dispute_opened
purchase.dispute_won
purchase.dispute_lost
Subscriptionssubscription.activated
subscription.renewed
subscription.past_due
subscription.canceled
subscription.expired

Signature and payload example

X-Discfront-Key-Id: dfwh_abc123
X-Discfront-Event-Id: twh_evt_123
X-Discfront-Event-Type: subscription.renewed
X-Discfront-Timestamp: 1779362531
X-Discfront-Body-SHA256: <raw-body hash>
X-Discfront-Signature: v1=<HMAC-SHA256>
{
  "version": "2026-04-22",
  "id": "twh_evt_123",
  "type": "subscription.renewed",
  "purchase": {
    "reference": "DF-80062-TH6UM5PU",
    "status": "paid"
  },
  "amount": {
    "value": "111.00",
    "currency": "EUR"
  }
}

Verify the signature against the unmodified request bytes before parsing JSON, then store the event id before applying side effects.

What matters

Why server owners use this

  • Not limited to Discord UI. Your connected systems can react to the same sale lifecycle.
  • Useful for real operations. Connect support, CRM, fulfillment, entitlement, and reporting workflows.
  • Delayed activation support. For configured license-key products, your software can send a signed activation callback before Discfront starts the access period.
  • Consistent event trail. Webhook delivery status can stay attached to the server record.
Webhook event layer Outbound delivery plus inbound activation for teams that need more than a role assignment.
Purchase paidPayment failedRenewalExpirationRefundDisputeRole access changedLicense key deliveredlicense_key.activatedDelayed key activation

Need webhooks for real operations?

Use Plus or Premium when Discord commerce also needs to trigger connected systems, or when software activation should start delayed license-key access.

Read webhook guide Join Community