After much thought I have decided I will no longer support or develop WePay Plugins. I have made this decision because I do not have the time and I can’t make the time to complete the updates.

I will also be ceasing development of all other plugins I have developed. I don’t have the time.

Things may change, but in the mean time this is where I am at.

Just a real quick post. There will be an update this week before the WePay API update cut off. This will patch all the plugins.

I will also release the new WordPress WePay plugin. It’s is basically a complete rewrite. So before Friday, there will be updates galore!

As some of you may know WePay has announced they will be getting rid of the widgets and buttons they offer. Since the email went out last week I have been getting many emails regarding this. In response to so many people I have decided it is best to build out some tools to fulfill this missing piece for many of you.

I cannot give an exact time but I should have it done in the next month or so. The plan at the moment is to provide a button system for the WP plugin and the some sort of basic button builder on my blog. Plans may change, for now it should help many of you and support your endeavors.

Please feel free to comment on this, send ideas, and or requests.

Just posted the updated files to the following WePay Plugins:

WePay Checkout 2.2 OsCommerce

WePay Tokenized Checkout 1.1 Oscommerce

WePay Checkout 2.2 Zen Cart

All plugins have received the latest version of the WePay PHP SDK. The code was also slightly cleaned up in the WePay Checkout 2.2 Plugin for OsCommerce.

Happy Thanksgiving to those in the US! I will be updating all the plugins I have built. Its been a long time coming and many fixes are coming.

Quick run down:

WePay WordPress Plugin: I will stop development of the API plugin and integrate it into this one. The WordPress plugin is going to be one large plugin instead of more then 1. I will also clean up the code a bit and throw in some documentation. And I will be getting rid of all the menu tabs and moving the WePay settings to the settings tab.

OsCommerce/ZenCart WePay Plugin: I will be cleaning up the code, fixing an issue with discount codes, and updating the sdk.

OpenCart WePay Plugin: Will be updating the sdk, cleaning up code.

Magento WePay Plugin: I will be releasing this free of charge in December.

WP Thumbs: I will be updating that a little bit. Setting it up so you can clear stats. Better control of placement, pages, posts, etc.

SimplyCaptcha: I will be updating the site, adding a registration form to get access to keys, and adding many more questions.


I will not say a specific time but it is coming soon. I’m looking at releasing some new WP plugins and I have some thoughts on a few OsCommerce plugins.


For anyone looking for a method to know that a user has completed payment from the iframe checkout without supplying the redirect_uri var, here is your method.

The WePay Iframe sends a PostMessage back to the parent window during the transaction. The message sent when the payment is completed is:

{ “wepay_message_type”:”iframe_checkout_complete”, “checkout_id”:”CHECKOUT_ID” }

Now there are many ways to handle this and the way I prefer is via Jquery. How I did this is using the plugin from Ben Alman. He has built a PostMessage plugin for jquery.

On the parent page make sure you have the plugin from Ben Alman and the lastest version of jquery.

Here is the script I came up with:

$.receiveMessage(function(e) {
if ("iframe_checkout_complete") > 1)  {
alert("Payment Processed");

There are many other ways to do this but I like this method. Simple and short. Easy to work with. When the customer processed the payment and gets to the order total page it will post a message saying “Payment Processed.”

I built this simple form to help users get API credentials faster from WePay. Some plugins have the capabilities to have the API credentials sent right to the plugin. With this form it will tell you if you can have the API credentials sent right to it or not.

When your using this form it will setup PRODUCTION API credentials. Their isn’t away to get staging. So, make sure you set your plugin to Production when using the API credentials supplied by this app.

Just released the new version of OsCommerce WePay Plugin. Its now 2.0!

Some of the new features include:

Request API credentials from the Plugin Directly

Prefill customer information on the checkout

New method of tracking order for the IPN.

For more information on this update see this post.


Whats Next

Update for ZenCart – 8/29/12

Update for WordPress – 8/30/12

Update for OpenCart – 8/31/12

A few new Plugins. 9/1/12


Tokenization plugins are about to roll out soon. There will not be a tokenization plugin for ZenCart. There will be for the other shopping carts and applications.


I have been really busy so for all of you waiting for me to respond you should get a email or comment shortly.

WePay News

There will be updates this week. I have a handle full of updates to all the plugins. As soon as they post I will post on here. There are also 2 new plugins posting. I will probably post them this weekend since I am currently wrapped up in code right now on other projects.


So I get slammed with spam all the time. I have tired all sorts of different capcha systems and plugins. I built a simple one a while back ago that works great! So I thought why not make a service for Simple Capcha and make a WordPress Plugin for it. And then Simple Capcha was born. The site will be up and running shortly and hopefully the plugin will be out in the next week. The features that Simple Capcha offers is full control of the look of your forms, or using a pre built capcha form. Its handled with JSON and POST calls to the server. All that is needed is your website address. The website address is needed to monitor usage. All accounts are free up to 5,000 requests a day for all websites under that account. You can register as many websites as you want under one account. Pretty sweet little system and it works flawlessly.

Expect to see a lot of posts this week.

Here is the word, WePay API is advancing and becoming more powerful then I have seen from many other API’s. Deploying plugins like I have built will become much easier in the near future. I’m extremely glad to say as a user of WePay, things will only get better!

Magento WePay Plugin
Yep, I have announced development of it. The exact date it will roll out is questionable at the moment. The current date I have set for it is July 12th, 2012. That date may change, and it more then likely will roll out sooner.

WordPress WePay Plugin 2.0
The long awaiting update only gets pushed back further. Sorry! More features and bug fixes have delayed release. I know the 30th was the planned date but now its probably closer to July 5th.

OpenCart WePay Beta to v1.0???
Its about to go to v1.0. Working with users right now to get it there. I know of at least 5 sites running in production mode under BETA 0.7, with about 15 more under staging mode in that same release. If your running 0.5 or 0.6 update asap, as there are issues with 0.5 and 0.6. I know a few of you have had issues getting it going and I’m working on setting up a couple tutorials. They should post right after this.

WordPress WePay Add-ons
If you liked the WordPress WePay API Plugin then you will love the up coming add on plugins. To mention a few the affiliate plugin, which uses tools like aweber, constant contact, and others to make the affiliate marketers lives better. S2 Member add on plugin is another in the works and should be pretty sweet when its done. The WordPress WePay API Plugin will be getting another update in the coming days. I have some additions and changes I want to make to improve the overall experience.

(Quick plug thanks to Thomas Butler and Tim Davis for the recommendations. Thomas not only introduced me to WePay and started this plugin building fest but he also gave me the ideas for the API plugin as well as the soon to release affiliate marketers plugin. Tim Davis intially sparked the idea of an affiliate marketer plugin, Thomas helped fill in the details. So thank you to both of you! As for the others sending ideas thank you!)

Beyond the tutorials I will throw up a few other posts on how to customize and other things related to WePay. Also all plugins pages will be getting a much needed FAQ thanks to the WP Super FAQ plugin. If you want to see faster updates and more features please donate.

I highly recommend all potential users of my plugins to read WePay’s TOS. We recently had someone try to sell guns and ammo with a plugin and found out they couldn’t after they spent all that time with integration of WePay. So check it out before you add your plugin. Future plugin updates will have the TOS in the read me.

This how to assumes you have already read this post:

If not I recommend you do.

1. Extract the plugin

2. Copy both folders directly into your OpenCart Installation, just drop it in there.

3. Once both folders are uploaded, login to your OpenCart admin login.

4. From there go to “Extensions > Payment”, Scroll down to WePay and click install on the right.

5. Now that it is installed you will click “Edit” on the right again.

6. You should now have a page that needs your API credentials, fill in the details and hit submit.

7. Test and confirm its working.


To start off, we are going to work in “staging” mode. What this means is its for testing only and when you run a transaction it will not actually charge anything it will just let you test everything out.

“Production” mode is when everything is running live and you want to charge cards.

When registering applications with WePay you have to understand staging and production are completely separate. This also means your API credentials are 100% completely different from staging to production. So when moving from one to the other you need to change your information as well as the account id!

This how to assumes you already have an account. Again if you registered at you still have to register at because they are separate sites.

1. Go to and login.

2. Once logged in go to

3. Click on “Register an Application”

4.  Fill in the account information

5. Submit and you will be brought to a page like I have below. For security reasons I have blanked out the account information.


As you can see you have the account id, access token, client id and client secret. This should be all the information you need to get your plugin working.

This how to is the same when you want to register for  production API credentials, but instead of going to, go to