Streamlining Your Payment Processes: Updates to Solidgate Integration - Solidgate

Streamlining Your Payment Processes: Updates to Solidgate Integration

Streamlining Your Payment Processes

Stay ahead in the rapidly evolving digital payment landscape with the latest updates to Solidgate’s integration system. Effective March 31, 2024, these enhancements, including revised webhook management and the introduction of new URL parameters, are designed to optimize your transaction flow.

Learn how these changes, from webhook customization to the new two-step payment procedure, can streamline your operations and ensure seamless, secure transactions.

Management of Webhook Notifications

Hard deadline: March 31, 2024

Currently, you send us a callback_url in each request, to which we send notifications for every order. Now, you have the option not to include the URL in the request but instead add it through This customization is done via the channel details (API credentials).

If necessary, we can assist you in setting this up in the hub immediately and jointly verify that everything is functioning correctly.

For more information about webhook notifications, please refer to the guide.

Status URL Deprecation

Hard deadline: March 31, 2024

If you are currently using the status_url, you need to replace it with a success_url and fail_url .

For example, in a recurring transaction, your request should be modified as follows:

 "recurring_token": "token_value",
 "order_id": "3445",
 "amount": 5900,
 "currency": "EUR",
 "success_url": "http://merchant.example/success",
 "fail_url": "http://merchant.example/fail"

Mandatory 2-step Payment Flow

Hard deadline: March 31, 2024

Solidgate introduces a mandatory 2-step payment flow, enhancing transaction security and compliance for both auto-settle and standard transaction processes.

  • If you use Solidgate’s auto-settle feature:
    • settle transactions by submitting authorization requests with the settle_interval parameter
    • monitor order statuses and void orders with declined transactions
  • If you don’t use the auto-settle feature:
    • submit authorization requests exclusively for valid transactions through the settle operation
    • always cancel mistaken authorization requests promptly using the void operation
    • process order statuses and void orders with declined and partial_settled statuses
  • Always secure authorization before submitting clearing transactions to maintain compliance;
  • Void authorizations that won’t be cleared within the defined time frame to prevent potential issues;
  • Process reversals for cardholder-canceled transactions and erroneous authorizations promptly.

If you use our subscription service, please note that you need to use actions auth-settle/auth-void for trial set-up. In case of a main billing period or product without trial, kindly use the auth-settle action instead of charge.

Kindly note that the maximum settle interval is 6 days (144 hours).

The Asynchronous Mode with Refund, Void, and Settle Transactions

Hard deadline: March 31, 2024

The asynchronous mode of operation involves flow:

  • The merchant initiates a refund, void, or settle request
  • Solidgate takes the request for processing and responds with an intermediate processing / created status
  • After processing the request, a notification arrives at the webhook URL with the final status of the order refunded / void_ok  / settle_ok

An external API reference contains sample data for refund requests, refund responses, and card order status webhooks.

Changes in Payment Processing for Apple/Google Pay Transactions

Hard deadline: April 1, 2024

Merchants using 1-click CIT (Customer Initiated Transactions) payment for upselling must mandatorily update their payment data processing flow. This is necessary to comply with new industry standards and only affects tokens received after payment through Apple/Google Pay.

What’s Changing?

  • Customer Initiated Transactions (CIT, 1-click): From April 1, 2024, as required by partner banks and according to Payment System Rules, we will no longer support tokens received after Apple/Google Pay for 1-click (CIT) payments or those where the customer is present on the site.
  • Merchant Initiated Transactions (MIT, subscriptions): For MIT transactions, the merchant can continue to use tokens received after Apple/Google Pay.
  • Integration Update: Please update your payment flows to call Apple/Google Pay buttons for all 1-click transactions (CIT) initiated by customers. If you are using a Payment Form, you can call it without the card part. For H2H calls of Apple/Google Pay, use the flow as for the first payment.

Share article

Start accepting payments today

Let’s discuss your business needs and we'll give you better fees and conversion rates than you have with your current payment provider.

    By clicking "Get in touch" you agree to our Privacy Policy

    Thank you

    Thank you

    We will contact you shortly. If you have any further questions, please contact us at