Plugin Author
RexAK
(@rexak)
Hi @analogknight,
Thanks!
CardConnect has recently made a change to their internal gateway that disables refunds for unsettled transactions by default, and a “void” needs to be called instead of a “refund” within the API. This ultimately presents a problem, as a item that is sent to be processed, or batched (Queued for Capture), is in a grey area, a sort of in between state, where we cannot know if we should issue a void or refund. After the item has returned from the Queued for Capture process, it is then refundable.
Until then, I plan to update the plugin this weekend to note this issue on the plugin’s homepage, and will continue to work with CardConnect to find a solution that will work.
This is not to say that refunds will not work, but to refund from within WooCommerce, you currently need to wait until the transaction has batched.
Just as a heads up, and on a separate reminder note, you’ll need to contact any shared hosting this weekend where you don’t have control of the firewall, and where you use our plugin, to make sure you have the FQDN fts.cardconnect.com opened in both directions, for ports 6443 and 8443.
Thanks for the quick reply. Makes sense. I wasn’t sure it it was something in the plugin or recent changes to Woo or WP that may have impacted it’s function.
Hostgator has kindly opened the ports and ip ranges as required for those changes. Though I may, read that as will, need to change hosts as the shared hosting on their service is way too slow for conducting business.
Plugin Author
RexAK
(@rexak)
@analogknight
Thanks for your understanding while we sort this issue out.
I’ll mark this as closed, and see if I can get you a personal update when this is resolved with CardConnect. Fell free to respond in a separate support thread if you need anything else.
