RexAK

@ccolotti I’ll need to get a copy of that and see if I can include its functionality.

When you open the CC settings page, then inspect in Chrome dev tools, do you see any console errors regarding the plugin and the new features?

This is what happens on a base install of WordPress/Woo/Subs/Pre-Orders:
https://snag.gy/psoeXk.jpg

@ccolotti
Which checkout editor plugin are you using, the official WooCommerce Checkout Field Editor, or…

@ccolotti
I’ve just added limited support for sending additional WooCommerce checkout fields to the virtual terminal custom user fields for transactions. Would you be able to give version 3.2.0 a spin and let me know what your results are? Some basic info is on the plugin page’s FAQ section.

@ccolotti Yessir….We were discussing the same this morning.
It may be even removed altogether, to prevent confusion in the future, if fts continues to be the only subdomain CardConnect will use. We’ll need to confirm with CardConnect first.

Appreciate you watching the forums and helping out when you can.

@ccolotti Is right. It should be just “fts”

That should solve your problem.

Hmm. Unfortunately, we cannot log in to your hosting account or get creds for it via this public forum. If you would reach out to your CardConnect rep, and tell them the situation, and have them put you in direct contact with us (the developer for this plugin) via a support ticket, they should be able to get creds from you and send them on to me. That may be worth a shot.

If you’re using a VPS, and are on a linux machine with WHM installed, perhaps you need to check your firewall setting in there?

All IPs, or just the Woo – CardConnect IPs?

Make sure you have them open the ports 8443 && 6443 for the Fully Qualified Domain Name (FQDN) of “fts.cardconnect.com” – CardConnect’s Woo info page has not been updated to show this info, and the IPs listed there will be changing.

Here is a copy of the ticket I put in for some of our SiteGround accounts:

Due to a payment gateway requirement, we need all of our hosting accounts to have the following address and ports opened in the firewall, for both incoming and outgoing, for merchant account processing:

fts.cardconnect.com:6443
fts.cardconnect.com:8443

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

@ccolotti
I’m going to mark this as resolved.

As an update, we found that Peoplehost, SiteGround, and HostGator have allowed the FQDN to be white listed for those ports.

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 @ccolotti,

Also, there will be an update to the plugin this week, that will have a little more details about this, in the WooCommerce CardConnect setting page.

Hi, yes this works with the latest Woo Version 3.6.1, WooCommerce Subscriptions Version 2.5.3, and WooCommerce Pre-Orders Version 1.5.13.

We’ll release an update soon to indicate this.

@ccolotti

Thanks for doing the research with SiteGround! The FQDN for you would be whatever CC sent you in your merchant package, but for most people using WP, you’re right, it would be “fts.cardconnect.com.”

If the FQDN whitelisting does work with SG – and they do not need to specifically open 2 range sets, then hopefully other hosting outfits can do the same. I’ll follow up with a SG ticket of my own to confirm.

Appreciate the assistance, again.

@ccolotti

Thanks for the link. I’ll reference this link in the next plugin update coming next week, to inform other users. I’ve got a call in with them for next week and we’ll see if we can get more info regarding the IP question.

I’ve marked the thread as unresolved, so we can keep up the conversation and open it to others, if needed.