# Revoked recurring token

Webhooks notify about a revoked recurring token for alternative payment methods.


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

Endpoint: POST APMRevokedRecurringToken
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: "alt_gate.recurring_token.cancelled"

## Request fields (application/json):

  - `token` (string, required)
    Recurring token.
    Example: "923bb4e6-4a5f-41ec-81fb-28eb8a152e55"

  - `initial_order_id` (string, required)
    Initial order identifier.
    Example: "22738n"

  - `cancelled_at` (string, required)
    Datetime when the token was cancelled.
    Example: "2024-12-21 11:21:30"


## Response 2XX fields