Rick Rottman

The Payeezy API specs that you use today to send payment data will continue to be supported for all Merchant IDs (MIDs) that have been upgraded from Payeezy to Clover

If you are using WP Payeezy Pay, you are not using an integration method that uses API. A plugin that uses API is WooCommerce.

WP Payeezy Pay only works with the Payeezy payment gateway. It does not work with Clover.

When your merchant account is switched from Payeezy to Clover, you will need to find a plugin that is compatible with Clover. WP Payeezy Pay is not compatible with Clover.

• This reply was modified 1 year, 4 months ago by Rick Rottman.

Bullet points appeared in the sidebar. I fixed it.

.sidebar-main .widget ul {
    list-style-type: none;
}

I have automatic updates turned on. Even if I didn’t, and first looked at the theme’s changelog before updating, I didn’t see anything in the changelog about changing list-style-type in the CSS.

Send me the URL of your donation page and I’ll take a look.

[email protected]

The basic version does not, but the premium version does.

https://richard-rottman.com/payeezy-payment/

Your code indicates you’re working with WooCommerce. WP Payeezy Pay is not compatible with WooCommerce.

The plugin isn’t designed to work that way. It cannot create invoices. Your best bet is to sign up with Invoice ASAP (invoiceasap.com). It’s compatible with Payeezy. It’s what I use when I send invoices. I pay monthly for the service. It’s $3.99 a month. You can also sign up for a full year and save 50% on the monthly fee.

I’m not an affiliate of the company. I don’t get any kick-back from them. Invoice ASAP is just what I use with my Payeezy account.

Is this even possible? If so how can this be done?

Not really. It would require integrating WP Payeezy Pay with one of the existing reCAPTCHA plugins. Personally, it’s not something I’m interested in doing. Mostly because it would be 100% useless.

If someone uses your payment or donation form on your website to test stollen credit cards, they are going to copy the HTML form you published and copy the parameters and use them to program their bot. They are not going to actually run the fraudulent transactions on your website.

The issue is that the reCAPTCHA on Payeezy is not stopping these fraudulent transactions. The bots fraudsters are using are able to get past Payeezy’s reCAPTCHA. I don’t know how, but they are.

The way to counter the fraud is to set up Velocity Controls on Payeezy:

https://support.payeezy.com/hc/en-us/articles/203731369-Velocity-Controls

This will stop the fraud in its tracks.

No, not really. To deposit donations into different bank accounts based on something the donor selects, you would need to have a different Payeezy account for each fund.

Even if you get a separate Payeezy account for each fund, there’s nothing off the shelf plugin wise that would facilitate that. I could custom code something like that, but neither this plugin or Payeezy Donate, the premium version would not be able to do that without some heavy customization.

Contact me directly if you have any more questions:

https://richard-rottman.com/contact-richard-rottman/

What’s going on is I messed up the last update. I had the state and country drop downs as well as the CSS files in separate folders to streamline things. I then ran across a website that was refusing to load the states, countries, and stylesheet. I elected to go back to including this data in the main plugin file.

What I forgot to do was clean up the PHP that referred to the states, countries, and stylesheets. I didn’t see the warnings because the website I used to test the plugin had warnings turned off. That’s what I get for using a live website to test a plugin.

I just pushed an update that resolves my mistake. Thank you for bringing it to my attention and I apologize for the confusion.

I went ahead and added a closing div to line 361. The theme I’m using for testing (Astra) never showed a problem. After I added the closing div to line 361, the published form looked the same. Weird.

The reason I added the get_file_contents is because I wanted to make the code easier to read. Moving the CSS and the dropdowns to separate files made things a lot easier for me to read.

Thanks again for letting me know. I appreciate the feedback!

I just updated the plugin to version 3.15.1. I put the step value back in. Thanks for pointing it out!

Thank you so much Brian!

I just committed an updated version (3.15) that should take care of the issues. I appreciate you letting me know about them. I wish I knew how the invalid type of “num” happened instead of “number.”

Thanks again!

The plugin is designed to pass information to Payeezy, not Contact Form 7. I wouldn’t be able to advise you on how to connect the plugin’s output to CF7.

Thanks for posting a link to the page! It made troubleshooting super easy.

It looks like you’ve posted the [wp_payeezy_payment_form] shortcode to the endpoint page. It will not work that way. The payeezy-endpoint page is created when you first install the plugin. It already has a shortcode that takes care of formatting the information collected in the form and creating a security hash based on your Payeezy account and the transaction. It should be left alone.

Remove the [wp_payeezy_payment_form] shortcode from the payeezy-endpoint page and publish it on a different page. Publish it and try again.