DocumentationAPI Reference

Webhooks Overview

Purpose

Webhooks provide real-time payment status notifications to your endpoint.

Configure at portal-test.sweuze.com → Developer → Webhooks.

Payload Structure

All webhooks follow this envelope:

{
  "id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "type": "payment_intent.succeeded",
  "version": "2025.1.0",
  "occurredAt": "2025-11-18T14:30:00.000+00:00",
  "data": {
    // Event-specific data (includes merchantId)
  }
}

Fields:

  • id: Webhook notification UUID (use for idempotency)
  • type: Event type (determines data structure)
  • version: API version of the webhook payload
  • occurredAt: ISO 8601 timestamp with milliseconds
  • data: Event-specific payload (contains merchantId and other fields)

Event Categories

Payment Intent Events:

  • Track payment intent lifecycle
  • data.intentId identifies the payment intent
  • data.merchantId identifies your merchant account
  • data.merchantReference matches your order ID
  • Contains customer, payment method, and status details

Payment Events:

  • Track transaction processing
  • data.intentId relates to payment intent
  • data.merchantId identifies your merchant account
  • data.merchantReference matches your order ID
  • Contains fee and error details

See Event Types for complete list with examples.

Security

Webhooks are signed with versioned signatures:

X-Signature: t=timestamp,v1=current_sig,v0=old_sig

See Signature Validation for implementation.