FAQ
Authorize.net New MasterCard and Discover Processing Requirements – Update
Thursday, May 20th, 2010 | General, eAuthorize 5.0 | Comments Off
Recently, users of Authorize.net where notified of changes to the gateway prompted by MasterCard and Discover modifying their rules concerning the processing of debit, prepaid and gift cards.We have been researching the impact of these changes on the eAuthorize plug-in and have determined that a modification will be required to keep the plug-in compliant. We have begun the process of updating the plug-in and expect release of eAuthorize 5.2 in September. Pricing for this upgrade has yet to be determined.
There are a few important things to note regarding these changes:
1- Simply installing the updated version of the eAuthorize plug-in will not automatically make your FileMaker database solution compliant with these changes. Some modification to the scripting in your database will be required to support the Balance Response, Partial Authorization and Authorization Reversal transactions outlined by Authroize.net
2- There is a danger that older versions of the eAuthorize plug-in will not continue to work after Authroize.net enforces these changes on June 30, 2011. To avoid this you should update to the latest version of the plug-in prior to that date.
3- If you are currently using eAuthorize 3.x or 4.x on Mac, you must be running FileMaker version 7 or later to upgrade to the 5.x version of eAuthorize. If you are still running FileMaker 6 or earlier on Mac, you will need to migrate your database to a later version of FileMaker to continue using the plug-in.
4- For more information on these changes please see the FAQ at Authorize.net
Check this space periodically for updates. New information will be posted when it becomes available.
eAuthorize 5.1 compatible with FileMaker 11
Monday, April 12th, 2010 | General, eAuthorize 5.0 | No Comments
WorqSmart is pleased to announce that we have tested eAuthorize 5.1 and can confirm that it is compatible with FileMaker 11.eAuthorize 4 not compatible with FileMaker 11
Monday, April 12th, 2010 | eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments
We have recently gotten several reports of eAuthorize 4 not working with FileMaker 11 on the Mac OS. After our own testing, we have found this to be the case. While eAuthorize 4 appears in the preferences list, you will receive the error message that the plug-in can not be enabled.The resolution to this problem is to upgrade from eAuthorize 4 to eAuthorize 5.1.
Registration Errors/Permission Errors
Tuesday, February 16th, 2010 | Events 3.0, Events 4.0, Events 4.5, FAQ, eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments
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?
Monday, February 8th, 2010 | FAQ, eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments
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?
Monday, February 8th, 2010 | FAQ, eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments
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?
Monday, February 8th, 2010 | FAQ, eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments
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 helpThe 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
Saturday, February 6th, 2010 | General, eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments
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!
Sign in to begin the verification process.
THIS IS NOT FROM AUTHORIZE.NET
eAuthorize 5.1.3 – Bug Fix Release
Monday, February 1st, 2010 | eAuthorize 5.0 | No Comments
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
Thursday, January 21st, 2010 | FAQ, eAuthorize 3.5 | No Comments
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.
