WorqSmart

Registration Errors/Permission Errors

dbader — Tue, 16 Feb 2010 21:11:43 +0000

Registering your plug-in by entering your license information in the plug-in configuration screen will sometimes fail due to permission issues (i.e. forgets the registration or cannot create registration) file on the installation computer. When this happens, typically it can be resolved by logging in with an account that has administrative permissions and then conducting the registration.

However, in cases of a networked computing environment that uses centralized authentication and application servers, there can still be problems with the permissions that prevent the plugin from storing and retrieving the necessary license info. The best resolution in such a case it to register the plug-in by using the plug-in’s built in registration function call.

From a startup script in your database, simply call the plug-in with the registration function and pass the necessary license code parameters. That way every time the database is opened the plug-in will be automatically registered.

Does data transfer via eAuthorize automatically or does it require a user interface?

dbader — Mon, 08 Feb 2010 17:35:23 +0000

It doesn’t require that you login to any interface on the payment gateway. You never have to leave your database to conduct the charge. You can fully integrate it into your database so you can pull up the record that contains the card info you wish to charge and press a button to execute a FileMaker script that will do the payment processing … instantly and without you ever having to leave your database.

Is the information sent via eAuthorize more secure, encrypted?

dbader — Mon, 08 Feb 2010 17:33:51 +0000

The information is transferred to the payment gateway over a standard Internet connection. The entire transfer is done using encryption to provide security as the credit card information and response is sent and received.

We currently pass credit card data to the payment gateway via an import file. How is eAuthorize different, can it help us?

dbader — Mon, 08 Feb 2010 17:32:35 +0000

If you are currently exporting your transactions from your database in a file, uploading that specially formatted file to a payment processor, and then the processor is running the transactions, eAuthorize can help

The advantage of eAuthorize is that it will send the transaction straight from the database to the gateway, and eAuthorize will be able to receive an immediate response back from the payment gateway as to whether the charge was approved or not. So, it’s instantaneous and it allows the scripting in the database to check the result of the charge so different things can be done depending on the result of the charge request. These are things you can’t do when you’re batch processing them via an upload file.

Phishing Email Scam Authorize.Net

dbader — Sat, 06 Feb 2010 16:35:52 +0000

We been alerted to a phishing email that many of Authroize.net merchants have been receiving. It appears to come from Authorize.Net and wants you to click a link to reactivate your account. Please don’t do this! If you receive any email that raises concerns with you, please contact Authroize.net immediately!

Here is what the email looks like:

Dear Authorize Customer,

We are sorry to inform you that your online services are expired, and must be renewed immediately, if you intend to use these services in the future, and prevent any similarly situations you must take action at once!

THIS IS NOT FROM AUTHORIZE.NET

eAuthorize 5.1.3 – Bug Fix Release

dbader — Mon, 01 Feb 2010 20:26:26 +0000

The purpose of this release is to correct three bugs that have come to our attention since the initial release of this product. These fixes are specifically for the the Paypal Gateway, as no other gateways were impacted by these bugs. If you are not using the Paypal gateway, no action is required at this time.

This release corrects the extra character problem which was causing additional characters to appear in Paypal settlement reports as wells as blocking AVS transactions on Paypal.

The release also corrects an improper formating issue which was causing test transaction to fail on the Paypal gateway.

If you are experiencing any of these issues with your eAuthorize 5.1 or 5.1.2 versions of the plug-in, simply download version 5.1.3 to resolve these problems.

eAuthorize 3.5 No Longer for Sale from our Website

dbader — Thu, 21 Jan 2010 23:56:02 +0000

Due to the recurring I/O exception error, and due to the recent changes to the PayPal gateway which render this product unusable on that gateway, we are removing this product for sale from our website.

If you are a Windows user and using the Authorize.net gateway and need additional copies of the plug-in, please contact Sales.

eAuthorize 3.5 – I/O Exception Error

dbader — Thu, 21 Jan 2010 23:30:50 +0000

Over the last month we have been receiving more and more reports of an I/O Exception error which causes transactions to fail. The error seems to be limited to users running any Mac OS and using the Authorize.net gateway. The error appears to be occurring across versions of the Mac OS and compatible versions of FileMaker. Windows users on the Authorize.net gateway do not seem to be experiencing this error.

We do not know what is causing this error. It could be a combination of a number of factors including but not limited to: product age, changes to the Mac OS or changes to the Authorize.net gateway.

We do know there appear to be two possible solutions for solving the problem.

1-Downgrade to version 3.0 of the plug-in. You can get the Mac version of the eAuthorize 3.0 plug-in by going to:
eAuthorize 3.0 Mac Download

Your existing 3.5 registration will work version 3.0. We are reasonable sure that this solution will work with up to version 7 of FileMaker and up to version 10 of the Mac OS. eAuthorize 3.0 will NOT work on an Intel Mac.

2- Upgrade to version 5.1 of the plug-in. Will eAuthorize 5.1 work for you? Yes, if you are using at least FileMaker 7 and a compatible Windows or Mac operating system. For more information on this product or to review requirements please see eAuthorize 5.1 Please be aware that there are some significant scripting changes that need to occur when upgrading from eAuthorize 3.5 to eAuthorize 5.1

WorqSmart Announces the Release of eAuthorize 5.1

dbader — Sun, 01 Nov 2009 00:03:05 +0000

It is with great pleasure (a little bit of relief) that WorqSmart announces the release of eAuthorize 5.1. This product update is in response to the changes made to the PayPal/Payflow Pro payment gateway. The changes make the gateway even more secure than it had been in the past.

Who Needs eAuthorize 5.1?
If you currently use eAuthorize with the PayPal/Payflow Pro gateway or if you are planning to use this gateway to authorize credit cards transactions from your FileMaker database, you will require eAuthorize 5.1. After January 1st, other versions of the eAuthorize plug-in used in conjunction with PayPay/Payflow Pro will not be compatible and transactions will fail.

If you are currently using the Authorize.net, Sage or PayPoint.net/SecPay gateways successfully with your current plug-in, there is no reason to upgrade at this time.

Pricing
There is no charge for this upgrade IF you have purchased eAuthorize 5.0 within 60 days of 10/31/09 release date. If you have not already, you will be receiving an email from us shortly.

If you have purchased eAuthorize 5.0 and it has been greater than 60 days from the release date, the upgrade price will be $29.95 per user. Please contact us at info@worqsmart.com to upgrade.

If you are upgrading from any other versions of eAuthorize, the upgrade price is $100.00 per user. Please contact us at info@worqsmart.com to upgrade.

Requirements
eAuthorize 5.1 supports Windows and Mac and is compatible with the following versions of FileMaker:

For Windows, all releases of FileMaker Pro between versions 5 and 10 are supported.  

For Mac, FileMaker Pro 7, 8, 8.5, 9 and 10 are supported.

eAuthorize 5.1 Status Update

dbader — Wed, 14 Oct 2009 15:42:38 +0000

We believe the stubborn bug, which was such a challenge to track down, has finally been resolved. Final testing is taking place now and we are hopeful to release Authorize 5.1 in the very near future. We will use this space to announce the release, so stay tuned.

Thanks to everyone for your patience as we work through the final testing process on the plug-in. We really appreciate it.