Credit Card Payments WordPress

Overview

 This script allows you to have a quick & easy payment terminal for your clients to pay with major credit cards (Visa, Master Card, American Express, Discover) on your WORDPRESS website without leaving it.

Installation and configuration of the script takes less than 5 minutes (however you do need to have SSL and one of 10 merchant accounts (PayPal, OptimalPayments, Moneris US or Moneris Canada, Authorize.net, Elavon, InternetSecure, Stripe, Payment Express, eWay or FirstData (linkpoint api) ). There are several options to pay:

1) Customers can input price themselves and type description.
2) You can pre-define services which your customer will pay for without asking them to enter payment amount.
3) or you can pre-define services which your customer will pay for AND allow them to enter price for that service selection.

Server Requirements

1) PHP 5.0+

2) cURL must be enabled to accept payments (contact your hosting provider if unsure).

3) SSL certificate must be purchased and installed on your server for your site in order to go live.

4) You must have an account with one of the supported gateways…

Installation

Fresh installation is pretty simple: 

1) Unzip plugin file.
2) Upload the the plugin folder (not just the files in it!) to your `wp-content/plugins` folder. If you’re using FTP, use ‘binary’ mode.
Your directory structure on FTP should look as following: wp-content/plugins/payment_terminal_pro/[…files..here…]
It is important to understand that since the file (zip) which you download from codecanyon contains not only plugin itself but documentation as well you won’t be able to install plugin by uploading through wp-admin plugins area. IT HAS TO BE INSTALLED MANUALLY BY UPLOADING FILES THROUGH FTP as outlined above.
3) Activate the plugin in your plugins administration panel.
4) Drag and drop credit card payment terminal widget from `Appearance/Widgets` area
5) Now go to credit card terminal settings and set your merchant account information!

Upgrade

First login to your wordpress admin and DEACTIVATE current plugin version.
Then unpack all the files from zip archive and OVERWRITE all files in wp-content/plugins/payment_terminal_pro folder.
Now login to your wordpress and go to plugins and activate new plugin

We do not recommend to use automatic plugin installer in wordpress with our file – simply because we have seen many cases
when customers were trying to upload the zip which they downloaded from codecanyon directly into wordpress plugin installer
which caused installation to fail, since the file which you download from codecanyon has not only plugin itself but also this documentation
and wordpress doesn’t see the plugin files then.

Shortcodes & Widgets

There are currently 2 shortcodes available:

1) [ccpt_paybutton] – use it to add “pay” button to any post/page on your blog.
2) [ccpt_paybutton id=”X”] (where X – service ID) – use it to add “pay” button for particular service you’ve setup in services section, can be added to any post/page.

At the moment plugins comes with 1 widget – which basically displays “pay” button which brings up the payment terminal window (default one)

How to use

After you activate plugin navigate to plugins settings section – you will be prompted to enter your codecanyon
username and license key. License key is your “item purchase code” which you need to obtain from codecanyon –
go to downloads section on codecanyon and click on download button next to credit card plugin -> select License Certificate

After both username and license key entered and activated – you will seee settings page with merchant providers logos
on the left side and their settings on the right side. All you need to do is click on your needed merchant logo and enter test/live settings
After that is done – scroll down and click save.

Next important step is to select currency from dropdown on the same settings page and enter admin notification email. When done- click save.

At this point you are ready to test payments on your site. You need to either set “show amount field” to YES – so that customers could enter amount which
they want to pay you (in case of donations, or if they’re paying an invoice for example) OR set it to NO and set “show services field” to YES – so that customers
could select pre-defined services from dropdown list (please make sure you create some services – in services section of our plugin). Another option would be to set both
amount field and services field to YES – in this case customers will be able to select service and set amount to pay you themselves.

The last thing left to do is to place either widget or shortcode on some post/page (or both). Please read shortcodes section in this documentation.

If you have any other questions – not covered here – plaese go to our support forums at http://support.convergine.com and start a new thread with your questions.

Live / Test Modes

Before going live – please make sure that you purchased SSL certificate for your site and that your hosting provider activated it on your account.
SSL certificate not only gives your customers piece of mind in terms of security – it is a requirement from most merchant providers to process live transactions.

To test if your site has SSL certificate – try adding https:// in front of your site, instead of http:// – if you don’t see any error messages, SSL is most likely installed.

After SSL is installed – go to plugin settings, and on the right side of your selected merchant tab – click “Turn Live Settings ON”
You will notice that some merchant gateways have both test/live API credentials boxes, and some just 1 with title TEST/LIVE – this means that
that particular merchant gateway doesn’t require or doesn’t provide test credentials and you can use your live credentials instead. 99% of merchant gateways
provide test environment, so even if you will enter live credentials into TEST/LIVE box – you still will be able to switch from test to live by clicking the same button
underneath the api credentials: when gateway is live (you will notice text change on the button itself, offering to switch to live or to test)

Moneris Test API

It is very important to use correct test API credentials for Moneris terminal. If it is wrong – you will receive NULL responses in test transactions.
Moneris Canada TEST API settings:
API TOKEN: yesguy
API URL: esqa.moneris.com
STORE ID: store1
When going live – API URL must be set to www3.moneris.com and API TOKEN and STORE ID should be taken from your account.

Moneris US TEST API settings:
API TOKEN: yesguy
API URL: esqa.moneris.com
STORE ID: store1
When going live – API URL must be set to esplus.moneris.com and API TOKEN and STORE ID should be taken from your account.

Where do I find my API Token?
Log into your Moneris Merchant Resource Center at either https://www3.moneris.com/mpg/index.php or https://esplus.moneris.com/usmpg/index.php depending on whether you have a Canadian or US account, respectively, then go to Admin > store settings > API Token where your 20-digit API token can be found.

FAQ & Common Errors

You can find all the frequently asked questions and common errors/solutions for this product in this section

Technical Support

We provide courtesy support for all our products to our valued customers within 48-72 hours after receiving the request through our support ticketing system. Each purchase comes with 6 months support time. After that – you may either purchase extended support through the marketplace or purchase premium support with us.

If you need any help regarding the installation of the script or any other question please read through respective product documentation first and if solution is not found – open support ticket (please note, you will need to register account and you will be required to provide your license key (item purchase code) during the registration process, which will then be validated through CodeCanyon API. If your support period has expired you may either extend it with Envato or purchasepremium support from us).

Please note that we do not provide support by email. Any email related to support and not to pre-sales questions will be replied to after any other support tickets are resolved and in general will be directed to open a ticket, since we need to validate your purchase/support period validity.

For more details about our support policy and terms of service (including what is and is not included in Basic Support) click here.

Our business hours are Monday – Friday: 9:00am – 6:00pm (EST), and support is provided only at that time. Upon opening a ticket, we make it our goal to respond within 48-72 hours, however depending on the issue you’re having it may take a bit longer, but in any case we will address the issue within specified period of time with at least “resolution time” in reply. 

Changelog

 

v3.3 – 04 August 2014
– fixed colorbox load issues (conflict with other plugins)
– pay button styling fixes

v3.2 – 31 December 2013
– added support for wordpress 3.8 and improved layout

v3.1 – 9 November 2013
– added support for wordpress 3.6, 3.6.1, 3.7, 3.7.1
– fixed eWay “invalid amount” issue
– fixed Moneris Canada issues with wrong API
– added Moneris Canada & Moneris US API test credentials to documentation

v3.0 – 7 May 2013
– improved admin interface
– updated authorize.net to our latest release
– updated paypal pro terminal to our latest release
– added credit card type guesser for front end form
– added payment express payment terminal
– added firstdata (linkpoint) payment terminal
– added eWay payment terminal
– added stripe payment terminal
– fixed shortcode issues
– added optimalpayments test environment
– fixed moneris thousands separator in amounts
– fixed wrong amount sent in email notifications
– fixed authorize.net thousands separator in amounts
– separated Elavon and InternetSecure in terms of processing code
– removed scriptaculous dependency

v2.0 – 18 January 2012
– added new payment gateway: Elavon/InternetSecure

v1.1 – 16 October 2011
– fixed 2 php short tags
– fixed optimal payments, moneris ca, moneris us, authorize.net terminals when using shortcode for particular service.
– paypal error 10571 is now treated as success in paypal payment terminal.

v1.0 – 9 August 2011
– initial release

Sources, Credits, Appreciation

We’ve used the following images, icons or other files as listed.

 

  • jQuery UI Library – http://www.jqueryui.com
  • jQuery Library – http://www.jquery.com
  • jQuery Colorbox – http://www.jacklmoore.com/colorbox
  • jQuery Tools – http://jquerytools.org/

Once again, thank you so much for purchasing our product.

Is this document useful? 1 0

Published: March 11, 2016 Updated: October 18, 2016

« back to all manuals