# Subscription payment updates

Webhooks for subscription status provide real-time notifications about changes in subscription status. 

The webhook structure is similar to the subscription status method but additionally includes the callback_type parameter in the response object.

There are two versions of subscription events: legacy and extended.
The extended version offers an enhanced webhook event set with more detail and context, giving merchants deeper insights into subscription stages for better management and analysis.
The legacy version remains supported until the end of June 2026.


  Duplicate webhook events can occur. Implement idempotency on your end to avoid processing the same event twice.


Parameters for each callback type can vary based on factors such as product type, payment method, trial availability, or other specific conditions.

Endpoint: POST Billing
Version: 1.0.0
Security: MerchantID

## Header parameters:

  - `merchant` (string, required)
    Unique public key provided upon registration and must be shared for identification purposes.
    Example: "wh_pk_7b197...ba108f842"

  - `signature` (string, required)
    Request signature that allows verification of merchant authenticity on the payment gateway server.
    Example: "M2E3OTkyNzcz...xMmExODI4"

  - `solidgate-event-id` (string, required)
    Unique event identifier.
    Example: "e1765cf7-70f7-4e56-8fb2-bd88744a94d1"

  - `solidgate-event-created-at` (string, required)
    Event creation time in ISO 8601 format with milliseconds.
    Example: "2025-06-05T12:34:56.789Z"

  - `solidgate-event-type` (string, required)
    Event type, indicating the specific event that occurred.
    Example: "subscription.updated.v2"


## Response 2XX fields