Our fix has been implemented and we are monitoring the results.
Posted Nov 18, 2020 - 11:15 CST
Update
A solution has been partially implemented. The issue should be occurring less frequently than before, and we are continuing to work on a full solution.
Posted Nov 18, 2020 - 08:29 CST
Identified
We have identified one cause for this issue and are working towards a solution. Completing this solution should coincide with the Payment Processing Environment Maintenance being conducted overnight, and we will continue to update as we make more progress.
Posted Nov 17, 2020 - 15:11 CST
Update
We are continuing to investigate this issue and work towards a solution. We have also gathered that capturing payment can result in a different error message saying "An error occurred while trying to process this transaction." and we have confirmed that this error is related to the others.
Posted Nov 17, 2020 - 08:29 CST
Update
We are continuing to investigate this issue and gather more information about it.
Posted Nov 16, 2020 - 14:51 CST
Update
We are continuing to investigate this issue, and we have gathered that Phone Orders may also encounter the error code 4001.143 with similar symptoms. All orders should still let you capture payment once the order exists in the system.
Posted Nov 16, 2020 - 11:43 CST
Investigating
We are currently investigating an issue where attempting to capture payment will result in an error code 4001.121. This issue does not appear to affect all orders, and payment can be captured on affected orders by simply trying to capture again. We will update this status page as we make progress on this issue.
Posted Nov 16, 2020 - 09:38 CST
This incident affected: Volusion Platform (Payment Gateway Services).