Help Center

Both void and refund operations come with associated reason codes. Void operations cancel transactions before finalization, while refund operations return funds to customers after transactions are complete.

0021 Solidgate – request by user

This code applies to any manual refunds initiated through the Solidgate Hub.

Monitor the frequency of these refunds to identify any patterns or common reasons that may be addressed to improve customer satisfaction.

0022 Solidgate – issuer fraud notification

This code is used when the issuer directly reports a fraudulent charge to Solidgate. Support team may initiate a refund after contacting the merchant.

Maintain close communication with Solidgate to understand the nature of these fraudulent activities. Consider implementing additional security measures if these incidents are frequent.

0023 Solidgate – risk department

Result of fraud detection. The customer can ask for a refund for the transaction.

Regularly review transactions flagged by the Risk Department to understand if legitimate transactions are being affected.

0024 Solidgate – retrieval request

When the issuer posts a retrieval request, the merchant may choose to refund the transaction.

If retrieval requests are frequent, review your transaction descriptors and customer communication to reduce misunderstandings that could lead to retrieval requests.

0025 Solidgate – prevention alert

Refunds are automatically issued when Solidgate receives a prevention alert.

Work closely with Solidgate to understand the triggers for these prevention alerts and consider tweaking your security settings or customer verification processes to minimize them.

0026 Solidgate – system error

This code is used rarely, only in case of technical problems between Solidgate, providers, and payment networks.

Report any system errors immediately to Solidgate support for troubleshooting. Review any commonalities in these errors to preemptively address technical vulnerabilities.

0027 Solidgate – antifraud

This code is used for automatic refund actions triggered by the antifraud system.

Consistently review and update your fraud prevention settings to keep pace with emerging fraud patterns. Coordinate with the Solidgate support to improve these settings.

0028 Solidgate – expired authorization

After the authorization expires, Solidgate may issue a void using this code.

Monitor the time between authorization and transaction completion to minimize instances of expired authorizations. Coordinate with the Solidgate support to potentially extend authorization periods if necessary.

0029 Solidgate – reversed by schemes

This rule applies when card schemes cannot confirm a payment authorization during the clearing process.

In such cases, to comply with card scheme requirements, the Acquirer/PSP must reverse (void) the original authorization transaction to release the blocked funds in the customer’s account.

Update the transaction status and ensure void requests are triggered at the appropriate point to avoid mismatches.

Track card order Webhook for further investigation.