WP Payeezy Pay

Description

Plugin creates a shortcode that when placed in the page or a post, generates a payment form for a Payeezy Payment Page. The published form includes:

  • First Name
  • Last Name
  • Company Name (optional)
  • Street Address
  • City
  • State (dropdown)
  • Zip Code
  • Country (dropdown)
  • Email Address (optional)
  • Phone Number (optional)
  • x_invoice_num (optional)
  • x_po_num (optional)
  • x_reference_3 (optional)
  • User Defined 1 (optional)
  • User Defined 2 (optional)
  • User Defined 3 (optional)
  • Amount (optionally recurring every month)
  • “Pay Now”, “Donate Now”, “Continue”, “Continue to Secure Form”, or “Make it So” button

Once a cardholder enters their information, they press the “Pay Now” or “Donate Now” button. They are then redirected to the secure Payeezy payment form hosted by First Data where they finish entering their information including credit card number, expiration date, and security code. The cardholder then clicks “Pay with your credit card” and the payment is made. Once the transaction is complete, the user is provided a receipt. They can then click a link and be redirected back to the original website.

Screenshots

  • Required Settings.
  • Optional Settings.
  • Optional Payment Fields.
  • Payment Page ID and Transaction Key in Payeezy.
  • Recurring Billing ID in Payeezy.

Installation

From your WordPress dashboard

  1. Visit ‘Plugins > Add New’.

  2. Search for ‘WP Payeezy Pay’.

  3. Activate WP Payeezy Pay from your Plugins page.

From WordPress.org

  1. Download WP Payeezy Pay.

  2. Upload the ‘WP Payeezy Pay’ directory to your ‘/wp-content/plugins/’ directory, using your favorite method (ftp, sftp, scp, etc…).

  3. Activate WP Payeezy Pay from your Plugins page.

Once Activated

  1. Visit ‘Menu > WP Payeezy Pay > and enter the Payment Page ID and the Transaction Key. These values are obtained in Payeezy. Also enter a currency code. If your account is setup for US Dollars, enter USD.

  2. Choose the Mode you wish to use, Live for a production account, one that actually processes credit cards, or Demo for a non-production testing account.

  3. Enter the Type of Transactions you want the Payment Page to make:

    • Payments – All payments are done on a singular basis.

    • Payments with optional Recurring – Customer has the option of clicking a box that will repeat their payment automatically in 30 days. If they don’t click the box, the payment is handled as a single payment. Recurring payment will continue until the Payeezy Merchant Administrator goes into Recurring and suspends or deletes the Recurring payment.

    • Payments with automatic Recurring – Customer doesn’t get a checkbox to make the payment recurring. The transaction will automatically be made again in 30 days and will continue until the Payeezy Merchant Administrator goes into Recurring and suspends or deletes the Recurring payment. Good for gym memberships, karate schools, etc.

    • Donations – Cardholder will have the option of making a donation by selecting a predefined amount. If none of the predefined amounts are optimal, they can select “Other” and enter their own. Instead of a button labeled “Pay Now” to go to the secure payment form hosted by First Data, the button will be labeled “Donate Now.”

    • Donations with optional Recurring – This is just like the above, but it gives the cardholder the option of making their donation on a monthly recurring basis by clicking a box. Recurring donations will continue until the Payeezy Merchant Administrator goes into Recurring and suspends or deletes the Recurring donation.

  4. Enter names for the optional payment form fields that you would like to use with your payment form. If you leave any of these fields blank, they will not appear on the published payment for. For example, if you want your customers to enter their invoice number on the bill they are paying, you would enter “Invoice Number” in the x_invoice_num field. A field will then appear on the published payment form for Invoice Number. The value entered by the cardholder will be passed on to Payeezy and it will be part of the transaction record.

  5. Press ‘Save Settings’.

Once Configured

  1. To add a payment form to a Post or a Page, simply add the ‘[wp_payeezy_payment_form]’ shortcode to content.

  2. Publish the Post or Page.

  3. That’s it!

FAQ

Installation Instructions

From your WordPress dashboard

  1. Visit ‘Plugins > Add New’.

  2. Search for ‘WP Payeezy Pay’.

  3. Activate WP Payeezy Pay from your Plugins page.

From WordPress.org

  1. Download WP Payeezy Pay.

  2. Upload the ‘WP Payeezy Pay’ directory to your ‘/wp-content/plugins/’ directory, using your favorite method (ftp, sftp, scp, etc…).

  3. Activate WP Payeezy Pay from your Plugins page.

Once Activated

  1. Visit ‘Menu > WP Payeezy Pay > and enter the Payment Page ID and the Transaction Key. These values are obtained in Payeezy. Also enter a currency code. If your account is setup for US Dollars, enter USD.

  2. Choose the Mode you wish to use, Live for a production account, one that actually processes credit cards, or Demo for a non-production testing account.

  3. Enter the Type of Transactions you want the Payment Page to make:

    • Payments – All payments are done on a singular basis.

    • Payments with optional Recurring – Customer has the option of clicking a box that will repeat their payment automatically in 30 days. If they don’t click the box, the payment is handled as a single payment. Recurring payment will continue until the Payeezy Merchant Administrator goes into Recurring and suspends or deletes the Recurring payment.

    • Payments with automatic Recurring – Customer doesn’t get a checkbox to make the payment recurring. The transaction will automatically be made again in 30 days and will continue until the Payeezy Merchant Administrator goes into Recurring and suspends or deletes the Recurring payment. Good for gym memberships, karate schools, etc.

    • Donations – Cardholder will have the option of making a donation by selecting a predefined amount. If none of the predefined amounts are optimal, they can select “Other” and enter their own. Instead of a button labeled “Pay Now” to go to the secure payment form hosted by First Data, the button will be labeled “Donate Now.”

    • Donations with optional Recurring – This is just like the above, but it gives the cardholder the option of making their donation on a monthly recurring basis by clicking a box. Recurring donations will continue until the Payeezy Merchant Administrator goes into Recurring and suspends or deletes the Recurring donation.

  4. Enter names for the optional payment form fields that you would like to use with your payment form. If you leave any of these fields blank, they will not appear on the published payment for. For example, if you want your customers to enter their invoice number on the bill they are paying, you would enter “Invoice Number” in the x_invoice_num field. A field will then appear on the published payment form for Invoice Number. The value entered by the cardholder will be passed on to Payeezy and it will be part of the transaction record.

  5. Press ‘Save Settings’.

Once Configured

  1. To add a payment form to a Post or a Page, simply add the ‘[wp_payeezy_payment_form]’ shortcode to content.

  2. Publish the Post or Page.

  3. That’s it!

Is this plugin an official First Data Payeezy product?

No. I use to work for First Data supporting their various e-commerce products. This plugin is independent of First Data Payeezy but was built using their sample code on my own time.

Reviews

Works great!

Super simple to setup and it just works without a bunch of bloated extra features.

Exactly What I needed

Very simple setup and easy to work with for what I needed. I did go in and add the ability to set a price and item description within the shortcode, however, so I could set it up for multiple products. Super easy to work with though: clean and simple code. Nice job!

Read all 8 reviews

Contributors & Developers

“WP Payeezy Pay” is open source software. The following people have contributed to this plugin.

Contributors

Translate “WP Payeezy Pay” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

2.83

  • Fixed a bug that wouldn’t use the x_invoice_num as x_description if x_invoice_num is being used.

2.82

  • Fixed a bug that wouldn’t allow a user to tab to the Country input.

2.81

  • Require a payment amount to be entered for non-donation payments. This was already required for donations.

2.80

  • Cleaned up the transansition page between the payment/donation form and First Data.

2.79

  • Corrected a few typos.
  • Linked field names with definitions explaining what they are and how they work.

2.78

  • Response Key field was mistakenly made a required field. I corrected that.

2.77

  • Converted Currency Code to a dropdown. Added Response Key field.

2.76

  • Removed the option of selecting x_type. It was causing intermittent errors on too many installations. Transactions will be processed as Authorization and Capture.

2.75

  • Fixed a bug that stopped the ability to change/update the currency type.

2.74

  • Changed the way the form uses CSS. It’s now included in the form instead of pulling it from a separate CSS file.
  • Changed the way the pay.php, donate.php, donate-rec, and pay-rec process x_type. The way it was included in the file was throwing intermittent errors.

2.73

  • Corrected an image link.
  • Added donation button.

2.72

  • Added the ability to process transactions as authorization-only transactions.
  • Corrected the spelling of “Provence.”

2.71

  • Added states and countries directly to the main plugin file.

2.70

  • Did away with the need to save the Transaction Key after upgrading the plugin to the latest version. It will now happen automatically during the activation process.

2.67

  • The transaction key file is now named after the Payment Page ID. This should enable this plugin to be used multisite.
  • Added the x_company field as one of the optional fields.
  • Add x_description back to the optional fields. I don’t remember ever removing it, so it must have been by mistake. I made it a textarea field since Payeezy doesn’t seem to have any character restrictions. Most fields are caped at 30 characters. This field has no such restrictions. I’ve tested it with hundreds of words without any errors. If you want a field for the cardholder to write a book, this is the one you want to use.
  • Removed unnecessary css from the admin screen.

2.66

  • State and Country selectors now show “Select a State” or “Select a Country” instead of the first option.

2.65

  • Changed the way the admin screen is styled.
  • Added the state selector and country selector dropdown values in a separate text file.

2.62

  • Fixed a problem that allowed donors to enter a negative custom amount.

2.61

  • Donors now not continue to First Data without first selecting an amount to donate.
  • If for whatever reason the Transaction Key file is blank and needs to be generated, an error message will appear at the top of any Admin screen advising that the “Save Now” button in Payeezy settings needs to be pressed.

2.60

  • Added the ability to change the text on the submit button.
  • Direct link to the stylesheet in the plugin editor.
  • Added a link to the WordPress plugin repository to make it easier to leave a 5-star (I hope!) review.
  • Added a warning message if the Transaction Key has not been saved.

2.53

  • Removed break at the end of every label.
  • Added an external stylesheet (wp-payeezy-pay/stylesheet.css) for the form so it can be modified, customized, copied, or manipulated.

2.52

  • Added a break at the end of every label.

2.51

  • Updated screenshots.

2.50

  • Moved Currency Code to the top of Required settings.
  • Now generates a message if Payment Page ID, Transaction Key, or Currency Code is not entered.
  • Added a link for a new add-on plugin, Payeezy Transactions.

2.45

  • Noticed I had placed Alabama twice in the dropdown.
  • Removed the link to WP Payeezy Transactions. I am not ready to make it live yet.

2.40

  • Added the ability to hard-code the amount the card holder will pay.
  • Added Response Key so that WP Payeezy Pay will be compatible with WP Payeezy Transactions, a premium add-on.
  • Updated the banner image and the icon image. The purple color was irritating me.

2.36

  • Removed two breaks and a horizontal line that was causing an annoying space before the form. Thanks Colette!
  • Updated the banner image and the icon image so it (hopefully) looks nicer in the plugin repository.

2.35

  • Fixed a problem with the currency code.

2.31

  • Fixed an image.

2.30

  • Tested to make sure it is compatible with WordPress 4.4.
  • Added Currency Code to the required settings.
  • Cleaned up the CSS to make sure everything looks pretty.

2.25

  • Minor changes involving support links.

2.2

  • Now the cardholder making a donation cannot proceed to Payeezy without picking an amount.

2.1

  • Made a change that strengthens security of the plugin. The Transaction Key is no longer visable in the HTML form. It’s now stored in a tiny file called key.php located in the plugin’s directory.

2.0

  • Combined this plugin with my other plugin, WP Payeezy Donate. All features found in that plugin are now rolled into this plugin. Going forward, this will be the only plugin updated, assuming updates are needed. If you select a Transaction Type option that supports Recurring and if you save the settings without entering a Recurring Billing ID, an error is displayed. If the mode is set to Demo, it now displays a notice. I also corrected a few typos and commented most of the code.

1.4

  • Added the ability to do Recurring.

1.3

  • Fixed a typo that wasn’t allowing x_reference_3 to work.

1.2

  • Removed Recurring. Was causing an error if no Recurring Plan ID was entered in the settings. The ability to add Recurring will be added back in a future update. Stay tuned!

1.1

  • Changed the field values to be required values if they are added to the form. If a cardholder leaves a field blank, they will be told the field is required before proceeding.

1.0

  • Initial release.