• Authorize.net / Planet Payment Setup
• Recurring Transactions
• Troubleshooting

If you are using PerlBill PRO and would like to use it with Authorize.net or PlanetPayment for processing transactions you must follow the steps below.

In the 'Merchant Settings' are of the Administration you are prompted for two pieces of information, the merchant username and password. You must enter these exactly as you use them to login to your authorize.net administration panel.

In your Authorize.net administration panel you must ensure that you have it setup so that PerlBill can establish a connection and post transactions. Please ensure:

a) In the Settings > ADC Referrer URL section you have NO URL's setup at all.

b) You must run PerlBill over an SSL secured connection (https://)

c) In the General Settings section, ensure the String Version is 3.10

When using the Pro version, the signup system alters to make way for collecting the added information from your clients. When placing an order your clients will be asked for a payment method (Cheque or Credit Card) and billing information.

If an order is selected as Credit Card the client will be billed when placing the order. If the purchase if one time only, your client's credit card details will not be stored. Credit Card storage is not recommended and is done at your own risk for recurring transactions.

If a plan is recurring and the payment method is Credit Card you will be prompted for a 'Encrypt Key' when approving the account. This key will be needed whenever taking any action against the card and must be entered to view the card number. It is recommended you do not use your admin password as you Encrypt Key.

• When I process a transaction is keeps getting declined
  

  Please ensure the three instructions in Section A have been completed. In your Authorize.net panel go to 'Transactions' and view the 'Current Batch' when viewing the batch click 'Declined Transactions'

  If your attempted transactions are listed, it is a problem processing them and is likely due to an AVS error or transaction error.

  If no transactions are listed this is likely because the connection was refused, normally this is due to one of the three requirements outlined in Section A not being met.