Rick Rottman

Sure. I’m just finishing up the new version. I’ll include that.

That’s the screen you get anytime something isn’t right when the request is sent to First Data. The values for x_fp_Sequence, x_fp_timestamp, and x_show_form are all added in the back end of the plugin. Since you’re doing donations, either donate.php or donate-rec.php adds that info with each donation.

Email me the URL to the published form so I can see what the problem is.

[email protected]

No, the basic plugin doesn’t support sales tax or additional fees. I’ve done custom integrations that facilitate that. I think it would make the setup more complicated if I added sales tax and additional fees.

Sorry about that. I fixed it and pushed out a new update, version 2.62.

This is what the payment page on my website:

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

Not without a customized modification. I can do that, you would need to submit a request at:

https://richard-rottman.com/premium-support/

I don’t offer a pro version per se, but I do offer to create a completely customized alternative for anyone needed multiple payment forms, multiple terminals, multiple recurring plans, etc. I charge $25 an hour and I base that on what I think it’s going to take me to code it.

I haven’t run into anything yet that’s taken over two hours. Most jobs take me an hour.

Where’s the payment form published at? You can send it to me in an email if you don’t want to publish it here.

[email protected]

Sorry for the delay in giving you an answer. The only time I get an error is when I try to make the payment a recurring payment. Have you enabled recurring in the payment page settings on First Data?

As far as making a user defined field appear in a different location, that would require some customization of the plugin. You can submit a support ticket by going here:

https://www.richard-rottman.com/premium-support-for-wp-payeezy-payment-page/

Yes. I’m rolling it out in the next update. I just want to do some more testing before making it public.

Also, sorry that it took me this long to reply. I didn’t get a notification that you posted a question.

Yes. Each field has its own ID that you can call to in your CSS file. For instance, to make the custom fields as wide at the form, you would want to add the following to the bottom of your theme’s CSS file:

input#user_1,
input#user_2,
input#user_3 {
width: 100%;
}

As far as the strange string of letters go, it looks like it’s being inserted by another plugin. You have something called Minify installed?

That’s been at the top of the list of my mental whiteboard for a long time now.

I’ve worked it out so I can pass the transaction data to a text file, but I haven’t figured out how to post it to the database. You don’t want anyone to be able to post to the database or even a text file stored on your website. It involves using the Response Key that you can generate in the Security section in the Payeezy Payment Page settings, and then hashing it with transactional information. If the hash that is sent to the Return URL matches what the plugin is expecting, then the transaction information is allowed to get through. If it doesn’t match, the information is ignored.

As soon as I get it all ironed out, I will release it in an update.

Yes. Did you want the cardholder to select how many payments they want to make or did you want that to be a choice in the plugin settings?

I’m not seeing that. Can you send me the link?

[email protected]

Thanks for pointing that out. I’ve made the change and rolled out an update.