Overview

[ { "title":"Access to API", "link":"https://docs.solidgate.com/payments/integrate/access-to-api/", "text":"Understand how Solidgate authenticates your API requests and provides validation errors.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/08/One-time.svg" } , { "title":"Integrate", "link":"https://docs.solidgate.com/payments/integrate", "text":"Explore Solidgate integration options, payment methods, and merchant website integration methods.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/08/Custom-Built-Rules.svg" } , { "title":"Testing", "link":"https://docs.solidgate.com/payments/testing/", "text":"Simulate payments to test your integration before launching in production.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/07/integration.svg" } ]

Sign In
Overview
Explore Solidgate's secure and seamless payment flows

Here, you can learn more about the payment flows for processing transactions through Solidgate, which will help you ensure a seamless integration.

Auth + Settle
anchor

This process involves the merchant obtaining authorization to hold a Customer’s funds, Solidgate communicating with the acquirer to process the transaction, and the merchant settling the transaction. Effective communication between Solidgate, the acquirer, and the merchant is crucial in ensuring a successful transaction.

ov_atst_1.0

  1. The merchant requests auth to hold the Customer’s funds, specifying the hold duration in hours.
  2. Solidgate acknowledges receipt and forwards the request to the acquirer for determination of auth approval.
  3. Solidgate receives the auth response from the acquirer.
  4. Solidgate processes the auth response and sends a Callback request with transaction status to the merchant.
  5. The merchant confirms receipt of the auth status to Solidgate.
  6. After the specified time interval settle_interval, Solidgate requests the acquirer to settle the transaction. The merchant may initiate partial settlement before the time interval expires, which will automatically void the remaining hold amount.
  7. The acquirer returns a settle response to Solidgate, confirming the transaction settlement.
  8. Solidgate processes the settle response and sends it to the merchant via a Callback request.
  9. The merchant confirms receipt of the transaction status to Solidgate.

3DS
anchor

This process is designed to enable secure and reliable payment processing through the use of 3D Secure authentication, which provides an additional layer of security to prevent fraudulent transactions.

ov_3ds_1.1

  1. The merchant collects card details from the cardholder and sends an appropriate request (auth or charge) to Solidgate.
  2. Solidgate acknowledges receipt, determines the transaction flow (2D or 3D), and sends a 3D Secure request to the acquirer.
  3. If the transaction is executable, the acquirer responds with the ACS URL.
  4. Solidgate sends the Verify URL with the ACS URL embedded to the merchant. The ACS URL connects to the card-issuing bank’s Access Control Server, where the Payer Authentication Request message is sent for customer authentication.
  5. When the customer opens the URL, Solidgate receives the Verify Request.
  6. After the customer interacts with the 3D Secure Page, the merchant sends the 3D Secure request to Solidgate.
  7. Solidgate requests the 3D Secure check status from the acquirer.
  8. The acquirer sends Solidgate the Verify Response, indicating transaction approval or decline.
  9. Solidgate processes the Verify Response and sends a Callback request with the transaction status to the merchant.
  10. The merchant takes necessary actions and confirms to Solidgate the receipt of the transaction status.

Void
anchor

The process involves the merchant obtaining authorization to hold the Customer’s funds and initiating a void operation if needed. Effective communication between Solidgate, the acquirer, and the merchant is crucial in ensuring a successful transaction.

ov_atst_1.2

  1. The merchant requests auth to hold the Customer’s funds.
  2. Solidgate acknowledges receipt and forwards the request to the acquirer for determination of auth approval.
  3. Solidgate receives the auth response from the acquirer.
  4. Solidgate processes the auth response and sends a Callback request with transaction status to the merchant.
  5. The merchant confirms receipt of the auth status to Solidgate.
  6. To initiate a void operation, the merchant sends a void request to Solidgate.
  7. Solidgate acknowledges receipt and forwards the void request to the acquirer.
  8. The acquirer returns a void response to Solidgate, indicating whether the transaction is declined or approved.
  9. Solidgate processes the void response and sends it to the merchant via a Callback request.
  10. The merchant confirms receipt of the transaction status to Solidgate.

Refund
anchor

The refund process involves communication and coordination between the merchant, Solidgate, and the acquirer to ensure the refund is processed successfully.

ov_rf_1.3

  1. The merchant submits a Refund request to Solidgate.
  2. Solidgate acknowledges receipt and forwards the request to the acquirer for determination of Refund eligibility.
  3. The acquirer returns a Refund response to Solidgate, indicating approval or denial of the Refund.
  4. Solidgate processes the Refund response and sends a Callback request with the transaction status to the merchant.
  5. The merchant takes necessary actions and confirms receipt of the Refund status to Solidgate.

Related articles FAQ

PSD2 & SCA
Solidgate GSA Fees description
Solidgate HUB - Dashboard
Solidgate HUB - Favorite filters management in HUB
Solidgate HUB - Event Log
Solidgate Terms
Payment Success Rate: What You Need to Know