RexAK

@in2itivedigital Apologies, please try the https://downloads.www.ads-software.com/plugin/cardconnect-payment-module.3.2.9.zip
version, as it does not use ReCaptcha. You should set this version to not auto-update, if you wish to use it.

Be advised, as of June 14th, CardPointe requires that ReCaptcha be present on your checkout page for WooCommerce.

@consultr @fluiditystudio I’m going to close this, as any changes to the plugin going forward must go through FiServe first, and that process can take some time.
It is on my list of things to add.
Hopefully, changes like this can be fast tracked in the future.

@rspector Then, I suspect there may be a plugin or theme code conflict.
Do you have a staging copy of your site? If so, try disabling other plugins, one by one, and check the checkout page each time. This would include any plugin that is not the main WooCommerce plugin, and of course, the CardPointe plugin. There may even be a conflict with one of the other payment gateways. Then, check if the theme itself has an issue, by switching to one of the default WP themes like “twenty twenty-one.”

@rspector
See if this version fixes that issue for you:
https://www.dropbox.com/s/qobutd181pnhd8r/cardconnect-payment-module-3.3.4a.zip?dl=1

If you’re on a newer version of WP, upload this via the dashboard and replace the existing version. Older versions of WP may need a manual upload via FTP.

It has a couple small tweaks to some Javascript, but otherwise the same exact plugin.
Let me know.

@maggiecameron Make sure you are using the ReCaptcha and Iframe settings. 3.3.2 does not ban cards or orders. We are looking into the issue internally, and once we have a reliable candidate, we can release a new version.

Thanks for your patience and understanding.

@maggiecameron Yes, I would advise that you roll the plugin back as soon as you can, and make sure you use the iframe setting for security reasons.

@amshishilla Interesting. That part of the plugin code has not changed in a very long time. I’ll look into it, and thanks for the update.

@in2itivedigital We are looking into making the new security options optional, as long as the site admins are aware of any risks surrounding carding events, and if we get approval for this change, we will issue a new update. Currently, due to massive amounts of fraudulent carding events during Covid, CardPointe deems this required.

@in2itivedigital I’ll see what I can do about messaging or the reset hook for an upcoming release.

@maggiecameron Thanks for the follow up. I’m going to close this thread, but feel free to re-open if you need assistance.
If you still have issues with the new 3.3.4 security features, please try downloading and using the 3.3.2 version until we can resolve your issue.
https://downloads.www.ads-software.com/plugin/cardconnect-payment-module.3.3.2.zip

Hi @amshishilla,

I will need to resume this tomorrow. I am leaving my desk for the evening. I will see the issue in my inbox when CardPointe sets this up for us.

Hi,

It looks like something is blocking “src” for the IFRAME’s card number field.

In the WooCommerce CardPointe settings, have you insured that the “Site” is set to “fts”?

see: https://tinyurl.com/yfsm8jfn

@amshishilla
Please confirm you have the payment gateway activated and setup.
You should use the IFrame Option, and make sure Autostyle is on.

When I visit your checkout page, after putting something in the cart, I see:
https://tinyurl.com/yjxqr8hy

Hi @maggiecameron
Are you able to use a plugin to clean up transients in your database? I suspect that old transients may be the cause.

After cleaning out the transients, set your CardPointe WooCommerce settings to for the new card tries to something higher.

Closing due to inactivity.