Authorize.net

From TMM Wiki
Jump to navigationJump to search
NATS 3
  Biller Instructions
NATS3 Biller List
123Bill
365Billing
2000Charge
Aconti Payment Service
Allopass
Ampay
Argus
Authorize.net
Bill1st Gateway
Billing Line
BoaCompra
Card Gate Plus
CCBill
CCBill Direct Pay
CCBill Web900
Centrobill
ChargeMeLater
ClearCard
ClearCard IDV
Commerce Gate
CurePay
DHD Media
E-Pay Company
Edelweiss Card
EGatePay
ElectraCash
EMerchantPay (Interconsult)
EnterCharge
Epoch
EProcessingNetwork
EuroBill
EPGBill.com
FABILLING
Global Access
GTBill
GXBill
HeidelPay
HeidelPay Gateway
iBill
ICN Ltd.
Infinity Payment
Interconsult
Jettis
Jettis Gateway
Jettis International
Linkpoint
LocalBilling
Merchant Partners Gateway
Merchant Partners Membership
Merchant Solutions
MyVirtualCard
Netbilling
Netbilling Native
NetCash
Netpay International
NoCreditCard
Oakbill
Optimized Payment System
Password by Phone
Pay4
Paygea
Payment Network
Paysite Cash
PhoneAccess
Plug'n Pay
PPPCard
Probiller
Protx
Pure Vanilla
RocketGate
RocketGate Native
RSBilling
SafeCharge
Secure Billing World
SegPay
Sonic Bill
StandardBill
Streamate
Symmetrex
TrustCash
TrustCharge
txtNation
Ukash
Universal Processing
Verotel Pro
VXSBill
WebBilling
WebPay
WTS
WTSeu
YNOT Processing
Zombaio
Netbilling v3 Upgrade Instructions
Purchasing Tokens Through Netbilling
Streamate Biller versus Third-Party
Switching From Epoch to Epoch EU
Epoch Member Approval Plus
Multiple Biller Accounts

Please don't test your biller setup with Authorize.net's test account—it won't work correctly.

Setting Up on Authorize.net's Website

Before you can begin configuring Authorize.net as a biller in NATS3, you must first register an account with them. This can be done through their website at http://www.Authorize.net/.

While registering with Authorize.net, make sure to take down the Login, Trans Key, and Duplicate Window that were provided to you by Authorize.net. This information will be necessary for setting up Authorize.net as a biller in NATS.

The following settings are not required by NATS, but we suggest you set them up anyway:

Setting Up Authorize.net in NATS

Billers Admin

To begin setting up Authorize.net as a biller in NATS, go to the Billers Admin. Scroll down to the "Biller" drop-down menu, select Authorize.net, and click "Add."

Note: If you don't see Authorize.net as a biller, put in a support ticket, as you may need an updated version of NATS.

When prompted, fill out your transaction and chargeback fees, along with when you wish to deduct them. Fill in the Login and Trans Key that were provided to you by Authorize.net under the "Account Info" section. If you were not provided with this information, please contact your biller to receive it.

The TransKey is generated by the Authorize.net and can be obtained using the following instructions on Authorize.net's website.

  • Log into the Merchant Interface
  • Select Settings from the Main Menu
  • Click on Obtain Transaction Key in the Security section
  • Type in the answer to the secret question configured on setup
  • Click Submit

We recommend you periodically change the transaction key. You have to disable the old key and generate a new key. The old key remains valid for 24 hours before it expires. To disable the old key on the Authorize.net Merchant Interface:

  • Log into the Merchant Interface
  • Select Settings from the Main Menu
  • Click on Obtain Transaction Key in the Security section
  • Type in the answer to the secret question configured on setup
  • Check the box that says Disable Old Key
  • Click Submit

Sites Admin

Next, go to the Sites Admin, create or edit a site, and scroll down to the "Biller Details" section. Find the "Authorize.net" settings, and enter a Duplicate Window value. This is how long the payment gateway waits after a transaction is submitted to check for a duplicate transaction. The value here must be between 0 to 28,800 seconds -- a maximum of 8 hours.

Once you have configured the necessary settings here, click "Save Changes." Your new biller should now be configured and ready to process transactions through NATS.

Authorize.net Notes

If you test transactions with Authorize.net, only the first one will show up. All test transactions are given user id 0 and NATS needs the user id to be unique.