Transaction management is a vital aspect of modern commerce. Solidgate’s suite of payment operations streamlines and secures transaction processes for your business. It incorporates token-based payments, 3D Secure verification, and real-time webhooks to enhance security and efficiency.

From initial charges and settlements to recurring payments, refunds, and ARNs for transaction tracking, the system ensures smooth payment flows and covers the full lifecycle of card transactions.


Charge

Via API Charge API
The charge request is designed to withdraw funds from cardholder accounts using 3D Secure technology for verification with auto-settle flow. This provides an optimized transaction process, offering flexibility in receiving funds and efficient payment processing, making it standard for transactions.

Recurring

Via API Recurring API

Recurring payment operations differ from charges by using a previously obtained token instead of direct cardholder data. After the first successful payment, you can leverage token system for recurring transactions. The token, containing essential payment method information, is accessible via the transaction card_token token field from:

With this token, initiate a recurring request using recurring_token. By default, the payment be route through the MID used for the initial transaction. Some recurring transactions, like 1-click payments, may require 3D Secure verification. The merchant must display the bank's ACS URL to customers, available through notifications or the check order status API request.

Technical recommendations for 1-click customer-initiated payment flow are

  1. Customer action: The customer initiates a 1-click payment.
  2. Token payment: Initiate payment using the secure recurring_token tied to the customer's payment information.
  3. Intermediate status: Immediately handle the intermediate status from Solidgate.
  4. Pre-loader display: Display a pre-loader indicating ongoing processing.
  5. Webhook and status polling: Set up a secure webhook for final order status.

Token-based 1-click payments are not supported for Apple Pay or Google Pay. Instead, you should re-triggered Apple Pay / Google Pay buttons by initializing the payment form with enabled false for the card section or using a new payment request.


Resign

Via API Resign API
Resign 1-click enables token-based transactions (1-click payments) with additional CVV verification, exclusive to PCI DSS certified merchants. Resign 3D Secure involves a resign request and a 3D Secure verify_url redirect.

Implement automated retry logic for declined operations. Additionally, consider incorporating a strategy to trigger subsequent attempts at hourly intervals, ensuring that the cumulative retry count does not exceed 120 attempts.

Refund

Via API Refund card order API
Solidgate handles refunds for both card payments and alternative payment methods (APMs) through its secure payment gateway integration.

A card payment refund is a request to return funds to the cardholder's account and can only be processed for successfully completed transactions.

Implement automated retry logic for declined operations. Additionally, consider incorporating a strategy to trigger subsequent attempts at hourly intervals, ensuring that the cumulative retry count does not exceed 120 attempts. Via Hub To make a refund

  1. Go to Payments > Orders.
  2. Select the needed order to go to the order details page.
  3. In the top-right corner, click on the Refund button.
  4. In the appeared form, complete the refund information:
    • Select Full refund or Partial refund
    • Specify the refund reason
  5. Click on Refund to confirm.
For currencies with 0 minor units, enter refund amounts without any punctuation to ensure correct processing.

To view a refund

  1. Go to Payments > Orders.
  2. Select Refund filter and choose a refund type:
    • All any refund
    • Failed no successful refunds
    • Full total refunded amount equals order amount
    • Partial at least one partial refund

Once the refund is successful , you can get the Refund confirmation on the Transactions section and share it with the customer. The refund confirmation serves as proof of a completed refund transaction and can be used for several purposes:
  • Share it with the customer as proof that the refund has been processed successfully, building trust and transparency in your business relationships.
  • Update your financial records to ensure accurate bookkeeping for tax purposes, track refund patterns, and maintain a clear financial history.
  • Present it to financial institutions if they have any inquiries about the transaction.

If a chargeback is opened, the refund option is turned off in both Hub and the bank’s system to prevent double payouts.

The process involves two stages:

  1. Refund initiation with processing status
  2. Refund completion with success status

After initiation, the status is marked as processing and after about one day, it updates to success once processed.

Refunds can be declined primarily due to the cardholder’s account being unable to accept them. The common reasons for a declined refund include:

Card or account issues

  • The cardholder has closed their account.
  • The account has been frozen due to suspected fraud initiated by the cardholder or the bank.
  • This prevents refunds from being processed.
  • The card does not support chargebacks, as some prepaid cards often do.
  • The issuer may have specific restrictions that prevent refunds via the original payment method.

Transaction issues

  • The cardholder has already disputed the transaction.
  • If the issue is related to a voided transaction, please note that a US bank cannot process a voided transaction for a non-US card. In such cases, the transaction can be completed, and the funds can be refunded within a day.
  • The order was created over a year ago, and the bank may recommend returning the funds using an alternative method, if possible.

Merchant issues

  • This makes transactions impossible. If this is the first case with a merchant, you should contact your account manager.
  • Refunds may be delayed due to frozen funds, which usually take 7-30 days to unfreeze.

In these cases, the advisable action for the cardholder is to reach out to their card issuer directly to resolve the issue.


Void

Via API Void API
The void request serves to nullify pre-existing auth transactions by revoking the initial authorization. Be advised that the void method can only be performed for auth transactions.

Implement automated retry logic for declined operations. Additionally, consider incorporating a strategy to trigger subsequent attempts at hourly intervals, ensuring that the cumulative retry count does not exceed 120 attempts. Via Hub To make a void

  1. Go to Payments > Orders.
  2. Select the needed order to go to the order details page.
  3. In the top-right corner, click on the Void button.
  4. In the appeared form, complete the void information:
    • Specify the void reason
  5. Click on Void to confirm.
It is important to specify the relevant void reason when performing this operation. Please note that the ARN for void can not be generated, so you can provide the ARN for authorization in this case.

Settle

Via API Settle API
The settle method ensures the settlement of previously authorized transactions. Be advised that if the subsequent settle amount is less than the initial auth transaction amount , the difference be refunded to the cardholder's account.

Implement automated retry logic for declined operations. Additionally, consider incorporating a strategy to trigger subsequent attempts at hourly intervals, ensuring that the cumulative retry count does not exceed 120 attempts. Via Hub To make a settle

  1. Go to Payments > Orders.
  2. Select the needed order to go to the order details page.
  3. In the top-right corner, click on the Settle button.
  4. In the appeared form, complete the settle information:
    • Select Full settle or Partial
  5. Click on Settle to confirm.
To avoid a 2.01 error code, ensure that you are not attempting to settle an order that has already been successfully settled. After receiving this error, please verify that the order status auth_ok .
To view a settle

  1. Go to Payments > Orders.
  2. Select Status filter and choose a settle type:
    • Settled fully settled orders
    • Partial settled orders with one or more settlements where the total settled amount is less than the order amount

Check status

Via API Check order status API
The check order status request helps to retrieve the present status of a given order. If a transaction is undergoing 3D Secure verification, the response indicates an order status of 3ds_verify value.

Get ARN

Acquirer Reference Number (ARN) plays a critical role in tracing refund transactions from issuing to acquiring banks.

This unique 12-character identifier allows cardholders to precisely track the refund process with their bank and located in the order details. ARNs are issued for:

  • refunds to track the refund back to the cardholder’s account
  • chargebacks to trace the disputed funds during the chargeback process

Please note, PayPal does not provide an ARN for refunds, recommend generating a Refund confirmation via Hub for order. Via API Get ARN codes API
The get ARN codes request obtains ARN codes for specific orders, providing essential information about refunds, currencies, and transaction statuses.

It is also possible to get arn_code for specific transaction: Additionally, you can get rrn_code Retrieval Reference Number (RRN) a 12-character identifier based on the ISO 8583 standard for transaction tracking. Via Hub To get ARN

  1. Go to Payments > Orders.
  2. Select the needed order to go to the order details page.
  3. In the Transactions section, click on Get ARN.
Not all banks provide ARNs, and ARNs are not generated for void transactions. For refunds initiated over 24 hours post-charge without an ARN in the Hub, please contact the Solidgate support team.