Subscribe for events on your Solidgate account, so your integration can automatically trigger actions

In Solidgate, asynchronous events for payments, subscriptions, and chargebacks are facilitated through webhooks, ensuring our clients receive all the necessary information. A webhook consists of a URL provided by the external application, and the payment system sends an HTTP request to that URL when a subscribed event occurs. Solidgate then sends a POST request to the merchant’s endpoint, containing event details in the request body.

The merchant's server subsequently processes the incoming request, utilizing its predefined business logic to handle the information.

Here are the general steps on how webhooks work in Solidgate:

  1. The merchant establishes an endpoint on their server for Solidgate to send webhook notifications.
  2. Register merchant’s webhook handler in the administrative HUB system. You will need to provide the URL of your handler and select the event types you would like to subscribe to.
  3. Upon the occurrence of a subscribed event, Solidgate dispatches an HTTP POST request containing event details to the merchant’s endpoint.
  4. The merchant’s server obtains and processes the request based on their established business logic.
  5. The merchant’s server returns an HTTP response to Solidgate, confirming the webhook’s receipt and processing.

It’s important to note that the merchant should ensure that the endpoint is always available and can handle incoming requests promptly to avoid missing any important notifications.

Receive webhooks

Webhooks can be managed within the Solidgate HUB by navigating to the channel settings located in the developer section.

Configure webhooks

It is feasible to configure up to 20 distinct endpoints for receiving the following event types:

  • Updated Card Order - reflects a change in the status of a card order
  • Updated Alternative Order - represents an update in the status of an alternative order
  • Updated Subscription - highlights a modification in the subscription or related order status
  • Received Card Chargeback - indicates the receipt of a new dispute for the card order
  • Received Card Prevent Alert - signifies the reception of an Issuer Network alert
  • Received Card Fraud Alert - denotes the acquisition of a TC40/SAFE alert

Receive events

Should you opt to receive identical events across multiple endpoints, webhook notifications will be dispatched to all specified endpoints.

Upon receipt of webhook notifications, your server must acknowledge and issue a 2xx HTTP status code response within 30 seconds. Failure to response will result in a webhook failure, prompting subsequent resending attempts.

Event types

Below is a list of events you can receive to automate your system, each accompanied by a unique signature for identifying Solidgate transactions in accordance with the API access rules.

  • Card order status Webhook
    Allows merchants to securely receive real-time card order status updates (e.g., processing or declined) and automatically initiate relevant actions or system changes.

  • Alternative payment methods order status Webhook
    Enables secure, real-time notifications for alternative payment methods (status processing or declined), allowing merchants to autonomously respond and update their systems.

  • Subscription status Webhook
    This webhook adds a callback type parameter with four options: init, renew, update, pause, resume and cancel

  • Chargeback Webhook
    Enables secure real-time chargeback event notifications for merchants, allowing automated system actions or updates based on these events.

  • Prevent alert Webhook
    Offers secure, real-time chargeback notifications for merchants, enabling prompt dispute resolution and loss minimization.

  • Fraud alert Webhook
    Enables secure, real-time fraud alerts for merchants, facilitating swift action to prevent losses.

Delivery attempts

If the webhook notification fails due to an incorrect response, the retry mechanism will automatically attempt to resend it multiple times.

We will attempt to deliver notifications according to the following structured schedule:

  1. 15 minutes after the initial failed notification
  2. 30 minutes after the first failed retry
  3. 1 hour after the second failed retry
  4. 2 hours after the third failed retry
  5. 4 hours after the fourth failed retry
  6. 8 hours after the fifth failed retry
  7. 16 hours after the sixth failed retry
  8. 24 hours after the seventh failed retry


Webhook event security is handled similarly to API authentication. In each notification, you will receive the Guide
Learn to authenticate API requests and generate signatures.
and Guide
Learn to authenticate API requests and generate signatures.
value in the headers.

  • The Merchant corresponds to the webhook Guide
    Learn to authenticate API requests and retrieve your credentials.
    public key
  • The Signature value is calculated using the webhook public and secret keys, which helps verify the authenticity and integrity of the webhook data transmitted between Solidgate and the merchant’s server.
    The data variable within the generateSignature function pertains to the payload transmitted via the webhook. This data can include event-related information, like order events, and is sent by Solidgate as part of the triggering HTTP request body.

You need to retrieve the merchant (wh_pk_) from the request headers and verify if you possess the corresponding credentials.

Generate a signature from the received body using the generateSignature function, as you would when sending a request to a gateway.

public function generateSignature ($ data)
  return base64_encode (
  hash_hmac ('sha512', $ wh_pk. $ data. $ wh_pk, $ wh_sk_)

Event handling

Occasionally, you may receive duplicate events, which can occur during notification retries or when resending requested events.

We recommend implementing idempotent processing in your integration to prevent the negative effect of duplicate events.

The unique event ID for each action is provided in the request header parameters, as outlined below:

Header Description Example
solidgate-event-id Unique event ID: a crucial identifier for monitoring and managing webhook events. e1765cf7-70f7-4e56-8fb2-bd88744a94d1

Related articles FAQ

Solidgate HUB - Webhooks endpoints settings in HUB