Q:  How can I fix a 3027 error when I try to use CyberCash3?
A:  A 3027 error is a CyberCash3 library initialization error. There are 3 probable causes.

1) Make sure you've set the DataDir property to a valid directory.
2) Make sure that the anonymous Internet user on your NT box has sufficient read/write access to the directory. This directory is used as a scratch area for the built-in CyberCash3 libraries.
3) Make sure that you've accurately typed or correctly copied-and-pasted (preferred) the CyberCashMerchantKey property.

Top

Q:  I'm not able to communicate with CyberCash?
A:  This is usually caused by your firewall not allowing A$PCharge to communicate with CyberCash.
If you are still having problems, set "charger.ProcessorLogging = true" in your script. When you attempt to clear the next credit card, the CyberCash libraries will create a file "CCMCK.LOG" on your C: drive.
This file is CyberCash specific and you may need to work with the CyberCash engineers to locate the exact problem.

From CyberCash:
Test the MCK with the built-in test merchant Cybercash ID (test-mck). Make a payment and check whether it passes through . This ensures the connectivity between your setup and Cybercash server. Making a successful payment through the test merchant implies your setup is right and you can now use the parameters that are associated with your Cybercash ID (CCID). In this way we can zero in on the problem.

Top

Q:  Why does my script run with no errors, but A$PCharge is not communicating with my processor?
A:  Make sure you don't have a charger.TestMode in there at all. If it says charger.TestMode=0 then it will act like all transaction clear. The TestMode property is used for testing. If you set the TestMode=3001, then it will simulate a 3001 error. It is primarily used to make sure your script handles the errors and reports the failures to the user in the way you want them reported. Make sure any references to TestMode are removed when you go live.

The demo A$PCharge object puts itself into TestMode automatically, so the next step would be to make sure you have the fully licensed A$PCharge installed and registered.

How to check...
1. Right click on the ASPCharge.dll.
2. Choose "Properties...".
3. Choose the "Version" tab.
4. The Description should be "ASPCharge" and NOT "ASPCharge DEMO".

Top

Q:  How can I tell if I have the DEMO or the LICENSED version of A$PCharge?
A:  The demo A$PCharge object puts itself into TestMode automatically, so the next step would be to make sure you have the fully licensed A$PCharge installed and registered.

How to check...
1. Right click on the ASPCharge.dll.
2. Choose "Properties...".
3. Choose the "Version" tab.
4. The Description should be "ASPCharge" and NOT "ASPCharge DEMO".

Top

Q:  Why can't I copy the licensed version of A$PCharge over the DEMO version of A$PCharge?
A:  The most likely cause is that A$PCharge is still in memory. You may need to stop your Web server, reboot and then copy the new licensed version over the demo version of A$PCharge.

If the copying is successful, you shouldn't need to re-register the licensed version. The CLSID is the same and the API is identical.

The only difference is that the DEMO is always in TestMode.

Top