Manage card payments

[ { "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/06/icon-customizable.svg" } , { "title":"Create your payment form", "link":"https://docs.solidgate.com/payments/integrate/payment-form/create-your-payment-form/", "text":"Understand how to integrate the payment form into your product.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-payments.svg" } , { "title":"Subscriptions", "link":"https://docs.solidgate.com/subscriptions/", "text":"Create and maintain a stable and healthy business subscription model.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-global.svg" } ]

Get in touch
Sign in
Manage card payments
Efficiently handle card payments using our 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 with 3D Secure support. 3DS 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
anchor

Charge API
The charge request allows withdrawing funds from cardholder accounts using 3D Secure for verification. For more control over transactions, you should send the type auth for 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 , allowing flexible capture and smooth payment processing.

Recurring
anchor

Recurring API
The use of a previously obtained token, not cardholder data, marks the difference between recurring payment operations and charges. Some recurring transactions, such as 1-click payments, may require 3D Secure verification.

To facilitate this verification process, the merchant needs to display a bank page (ACS URL) to the customer. This page can be obtained through notifications or the check order status API request from the merchant end. Technical recommendations for 1-click customer-initiated payment flow are as follows:


  1. Customer action: The customer initiates a 1-click payment.
  2. Token payment: Initiate payment using the secure token tied to the customer's payment information.
  3. Intermediate status: Immediately handle the intermediate status received from Solidgate to prepare for the next step.
  4. Pre-loader display: Show a pre-loader on the interface to indicate that the payment process is ongoing.
  5. Webhook and status polling: Set up a secure webhook to receive the final status of the order. Optionally, implement background polling to periodically check the order status as a backup.
By following these points, the merchant can effectively handle a 1-click, customer-initiated payment process.

Resign
anchor

Resign API
Resign one-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 verification URL redirect.

We recommend implementing 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
anchor

Refund card order API
Solidgate handles refunds for both Guide
Accept and manage credit card payments from your customers. Cards are the most popular payment method globally, offering convenience and widespread acceptance. card payments and 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. alternative payment methods (APMs) through its secure payment gateway integration.

A card payment refund constitutes a transactional request to revert funds to the cardholder's account, and it can only be executed for successfully completed transactions.

We recommend implementing 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 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.
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.

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

  • Prepaid cards: The card does not support chargebacks, as some prepaid cards often do.
  • Frozen account: The account has been frozen due to suspected fraud initiated by the cardholder or the bank.
  • Suspected fraud flagged by the issuer: This prevents refunds from being processed.
  • Closed account: The cardholder has closed their account.
  • Disputed transaction: The cardholder has already disputed the transaction.
  • Unable to accept the refund: 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.
  • MID closure: this makes transactions impossible. If this is the first case with a merchant, you should contact your account manager.
  • Frozen funds: 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
anchor

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 executed for auth transactions.

We recommend implementing 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 Guide
Analyze refund reasons to boost revenue and gain insights into business operations. void reason when performing this operation.

Settle
anchor

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

We recommend implementing 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.

Check status
anchor

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 Guide
Orders can also go through various other states, such as 3ds_verify, approved, declined, refunded, etc. order status of 3ds_verify .

Get ARN
anchor

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:

  • 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.

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.
Get ARN codes API
The get ARN codes request obtains ARN codes for specific orders, providing essential information about refunds, currencies, and transaction statuses.
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.

Webhooks
anchor

Card order status Webhook
Webhooks allow merchants to receive real-time notifications of card order status changes, such as the final status of refund, void, and settle transactions, and automate system updates or actions based on these events. To prevent processing duplicates, ensure idempotent handling by logging and checking event IDs.

Network token created Webhook
Receive real-time notifications when a network token is issued by Visa or Mastercard, allowing for automatic system updates. Implement idempotent processing to avoid handling duplicate events.

Network token updated Webhook
Get notifications when a network token is updated, facilitating timely system adjustments. Use idempotent event processing practices to manage potential duplicate notifications.

Chargeback Webhook
Webhooks for chargebacks enable real-time alerting of chargeback events, aiding immediate action or system update. Log event IDs to ensure each is processed only once.

Prevent alert Webhook
Utilize webhooks to preemptively address and resolve issues before they escalate, ensuring smoother transaction processing.

Fraud alert Webhook
Securely receive fraud alerts through webhooks, which notify of fraudulent activities reported by card schemes and enable rapid response.

Insights
anchor

When dealing with payments, it is crucial to differentiate between an order and a transaction as they have distinct meanings and implications.

Solidgate order logs are stored for 30 days.

An order is essentially a customer’s request to purchase goods or services, which serves as a record of a planned purchase. In Solidgate, an order and its associated transaction go through different stages, each of which helps move through the payment processing steps, from initiation and verification to the final state - approval, rejection, or settlement.

Solidgate offers a Guide
The card orders report provides comprehensive insights into transaction processing and customer data, allowing merchants to optimize financial tracking and operational strategies. reporting solution to deliver detailed transaction data for card orders. This tool enables tracking order statuses, managing reconciliation, and gaining actionable insights into customer behavior.

Order status
anchor

Value Final state Description
created No This is the initial state of an order, indicating its creation. It remains in this state until a payment attempt occurs.
processing No An order enters this state when payment is first attempted and stays here until a payment is captured.
3ds_verify No This state is for orders undergoing 3D Secure verification, either triggered by a payment request with a 3D parameter or additional verification by Solidgate or the issuing bank.
auth_ok No Indicates successful reservation of funds for the transaction.
auth_failed Yes This state indicates a failure in reserving funds.
void_ok Yes The reservation of funds has been voided.
approved Yes The order is approved, and the payment is successfully processed.
declined Yes The order was declined.
settle_ok Yes Reserved funds have been successfully captured.
partial_settled Yes A portion of the funds has been captured.
refunded Yes Funds by the order were Guide
The refund involves coordination between the merchant, Solidgate, and the acquirer for successful processing. transferred back to the cardholder.
The final state denotes whether an order can remain in that state until subsequent actions such as void or refund, as part of logical system processing.

Transaction status
anchor

Value Description
created The transaction was created.
processing The transaction is currently undergoing processing.
verify The transaction is undergoing 3DS verification, and the customer should be redirected to the ACS URL provided to finalize the payment.
success The transaction has been successfully processed.
fail The transaction has been rejected. Refer to the Guide
Understand why the payment is declined and how you can resolve it. error code for additional information.

Transaction type
anchor

Value Description
pay The operation of charging, which includes authorization and capture in a single transaction.
recurring The operation of executing payments using a token for repeated transactions.
recurring-auth The operation of reserving funds using a token.
refund The operation of transferring funds back to the cardholder.
resign The operation of executing payments using a token in conjunction with CVV.
resign-auth The operation of reserving funds using a token and CVV.
auth The operation of reserving funds.
settle The operation of settling reserved funds.
void The operation of cancelling a reserved fund.
apple-pay The charge via Apple Pay.
google-pay The charge via Google Pay.
Looking for help? Contact us
Stay informed with Changelog