Manage card payments

Manage card payments
Efficiently handle card payments using payment operations framework

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, Guide
Boost payment security and reduce risk with 3D Secure support.
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 Guide
Explore Solidgate's secure and seamless payment flows.
payment flows
and covers the full lifecycle of card transactions.


Charge

Charge API
The charge request is designed to withdraw funds from cardholder accounts using 3D Secure technology for verification with Guide
Auto-settle is a feature that automatically settles orders if you provide a settle_interval value in your charge requests with the type auth.
auto-settle
flow. This provides an optimized transaction process, offering flexibility in receiving funds and efficient payment processing, making it standard for transactions.

Recurring

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 a 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 routed 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 Guide
    Subscribe for events on your Solidgate account so your integration can automatically trigger actions
    webhook
    for final order status.

Token-based 1-click payments are not supported for Apple Pay or Google Pay. Instead, you should re-triggered Guide
Optimize your payment form with Apple Pay integration, providing a secure and efficient checkout for Apple device owners.
Apple Pay
/ Guide
Enable Google Pay button to give your customers more payment options.
Google Pay
buttons by Guide
Understand how to integrate the payment form into your product.
initializing
the payment form with enabled false for the card section or using a new payment request.


Resign

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

Refund card order API
Solidgate handles refunds for both card payments and alternative payment methods Guide
Connect alternative payment methods to boost your checkout conversion. Solidgate offers diverse payment methods, aiding merchants in understanding and catering to local preferences globally.
(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.
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.

Full refund returns the entire refundable amount in one operation.
Partial refund returns only part of the amount; you can perform multiple partial refunds until the total refunded amount reaches the original paid amount.

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.


Use these checks to troubleshoot and handle refunds

  • Monitor order updates Via API with Updated card order Webhook and validate the latest status with Check order status API
  • Track the final refund state Via Hub on the order details page Transactions section
  • Ensure the order is in a refundable final state, because a refund is not available for non-final flows, for example, 3ds_verify or processing state
  • For Guide
    Invalid 3DS flow that prevents successful authentication completion.
    2.12
    cases, the refund can be unavailable because funds were not captured
  • For Guide
    The issuing bank blocked the transaction due to suspected fraudulent activity.
    3.10
    or Guide
    The card in use is lost, all transactions are restricted.
    4.04
    issuer/card restrictions cases, ask the cardholder to contact the issuer and share ARN when available

Refunds may 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, unlike some prepaid cards.
  • The issuer may impose restrictions that prevent refunds to the original payment method.

Transaction issues

  • Refund time limits are not universal and may vary by card scheme, issuer, and acquirer/PSP rules for the specific MID.
  • 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.
  • If the order was created more than a year ago, the bank may recommend returning the funds via an alternative method, if possible.
  • If you need a scheme or acquirer-specific confirmation before initiating a refund, please contact us .

Merchant issues

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

In these cases, the cardholder should contact their card issuer directly to resolve the issue.

Retry only transient failures and avoid repeated retries for hard declines, for example, Guide
The customer has blocked transactions via this card for reasons that require clarification or the account is closed and all transactions are restricted.
closed
accounts or Guide
The card cannot be used to make this payment (it is possible it has been reported lost or stolen).
restricted
card. If funds are not visible within the expected timeline, provide ARN/RRN and ask the cardholder to contact the issuer.


Void

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.
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 Guide
Analyze refund reasons to boost revenue and gain insights into business operations.
reason
when performing this operation.
Please note that the ARN for void cannot be generated, so you can provide the ARN for authorization in this case.

Settle

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.
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 Guide
“Invalid data” code message is used for validation errors, with the reason for the validation triggering specified in the body, object error, of the response.
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 Guide
An order is a customer’s request to purchase goods or services, progressing through various states based on payment status.
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 lower than the order amount

Check status

Check order status API
The check order status request helps to retrieve the present status of a given order. If a transaction is undergoing Guide
Boost payment security and reduce risk with 3D Secure support.
3D Secure
verification, the response indicates an order Guide
An order is a customer’s request to purchase goods or services, progressing through various states based on payment status.
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 acquirer-assigned identifier allows cardholders to track transaction movement with their bank and is shown in order details.

ARN is typically a 23-character alphanumeric value, depending on card scheme and acquirer format.

ARN available for settled and refunded transactions, but is not generated for voided, auth, or failed transactions. It is generated asynchronously after clearing data is received from providers, so it may be unavailable immediately after settle/refund.

ARN is used for:

  • Guide
    The refund involves coordination between the merchant, Solidgate, and the acquirer for successful processing.
    refunds
    to track the refund back to the cardholder’s account
  • Guide
    Manage chargebacks effectively to minimize losses and protect your business.
    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.
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.
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.
If ARN is not visible in Hub more than 24 hours after a settle/refund operation, please contact us .

Looking for help? Contact us
Stay informed with Changelog