24/7 Support: 800.608.6482

Get Started

Reference Guide

Authorize.Net Payment Services v3.1

Authorize.Net has three payment methods:

  • AIM (Advanced Integration Method)
  • CIM (Customer Information Manager)
  • SIM (Server Integration Method)

Miva Merchant only supports AIM. This is a traditional payment gateway and the one most commonly used by Miva Merchant store owners. Authorize.Net AIM does not provide merchant accounts directly, but it can connect to almost any merchant account.

Login ID: Enter the Login ID and Transaction Key that you created when you set up your AIM account. The Login ID and Transaction Key are specific to your Miva Merchant store and are different from the credentials that you use to login to Authorize.Net.

Transaction Key:

To find your Authorize.Net Login ID and Transaction Key:

  1. Log into your Merchant Interface at https://account.authorize.net.
  2. Click Settings in the main left side menu.
  3. Click API Login ID and Transaction Key.
  4. Under Create New Transaction Key, enter your Secret Answer. Note: When you get a new Transaction Key, you can choose to disable the old Transaction Key by clicking on the Disable Old Transaction Key(s) box. You may want to do this if you suspect your old Transaction Key is being used fraudulently. If you check this box, the old Transaction Key expires immediately. If you do not check this box, the old Transaction Key will automatically expire in 24 hours.
  5. Click Submit.

Authorize.Net URL: The URL that Miva Merchant uses to submit requests. This field is autopopulated. You should only change it if you are given a new URL by Miva Merchant or Authorize.Net.

MD5 Hash Security Code: The hash is an additional security feature from Authorize.Net. Enable the hash feature in your Authorize.Net account and enter the hash string they give you here. When a customer begins a credit card transaction, the hash string is set from your on-line store to Authorize.Net as an extra credential.

See https://support.authorize.net/authkb/index?page=content&id=A588

Duplicate Window Duration: Measured in seconds.

When your on-line store sends a request (authorize/void/capture/refund) to Authorize.Net, Miva Merchant starts a timer. If an identical request (same credit card number, order number, and order total) is sent to Authorize.Net in the duration you set in this field, the first request is kept and the other requests are considered duplicates and are ignored.

The text that you enter in this field will appear in your on-line store during checkout when your customer enters their credit card information. Merchants usually use this field to describe the purpose of the CVV2 field.

Charge Method:

Online (Automatic Capture): Authorize and Capture happen right away.

Offline (Authorize Only, Capture Later): Authorization occurs when the user clicks the Submit button in the Payments page in your on-line store. To capture funds you must edit the order in Miva Merchant admin and click on the Capture button.

Note that these settings also affect you when you manually create an order. For example:

  1. Set the Charge Method to Sale (Automatic Capture).
  2. Manually create an order.
  3. Edit the order and click the Authorize button. In the Authorize dialog box, select a payment type associated with PayPal Payments Advanced and click OK.

In the Edit Order screen, you can see that the Capture button is greyed out and the funds were automatically captured after authorization.

Use Secure Source Validation: This feature is available to you if you have a merchant account with Wells Fargo, and they sell you an Authorize.Net account. Please contact Wells Fargo customer support to see if this option is the right choice for your account. If you enable this option, when your on-line store sends a request to Authorize.Net, your Login ID from Authorize.Net is replaced with a credential from Wells Fargo.

Store Entire CC Number: If you select this option, the customer's entire credit card number is attached to the order. If you do not select this option, only the last four digits of the customer's credit card are attached to the order.

Test Mode: Enable this option if you want to run test credit card transactions.

  1. Check this box to enable test mode in Miva Merchant.
  2. Login to your Authorize.Net account and set your account to test mode.

Discard Failed Order ID: This feature has been superseded by the Duplicate Window Duration setting. If you are using Discard Failed Order ID, it will still work, but it is no longer needed.

If you enable this option and the customer's credit card fails to authorize:

  • The customer stays at the Payment Information screen (OPAY). Any failure message that was generated by the gateway is displayed on this screen.
  • A new number is created for the order.
  • The customer must wait two minutes to resubmit the order. The delay is needed to force Authorize.Net to discard their order number, so that the new Miva Merchant order number is matched with a new Authorize.Net order number.

Please note that this option can cause errors if you are using a thirdparty module that takes any action with the order number. A third-party module has no way of knowing that the order number has changed and can take actions using an order number that Miva Merchant has deleted. This is not a problem for modules created by Miva Merchant, since those modules will be "aware" that the order number has changed.

If you do not enable this option and the customer's credit card fails to authorize:

  • The customer stays at the Payment Information screen (OPAY). Any failure message that was generated by the gateway is displayed on this screen.
  • The order number remains the same.

The customer can re-submit their order immediately

Available Payment Methods: Electronic Debit: This is an eCheck product from Authorize.Net that allows your customer to pay by entering their checking account information in your on-line store.

As the merchant you pay a monthly fee to Authorize.Net for the eCheck service and a flat fee per transaction. There is no "discount fee" (a transaction fee that is a percent of the order total) for an eCheck. When the customer reaches the Shipping/Payment Selection screen (OSEL), they choose Electronic Debit from the Pay With drop-down list. You can change this text by editing the code in OPAY > Page tab > Template field.

Pay With

In the Payment Information screen (OPAY), the customer enters their checking account information:

Electronic Debit

Require CVV2 in Administrative Interface: This option only affects you when you are manually creating an order through the Miva Merchant admin interface. If you enable this option, you must enter a CVV2 number in the Authorize dialog box when you create or edit the order. If you do not enable this option, the Authorize dialog box will still have a CVV2 field, but you can ignore it.

Looking for Developer Docs?

We have a whole section for that, including: Developer Training Series, Template Language docs, Module Development tutorials and much, much more.

Head to the Developer Section

Miva believes that all online businesses should have access to a scalable ecommerce platform that can meet their unique business requirements. Miva offers PCI compliant ecommerce, hosting, and custom website design and development solutions. Miva customers have processed over $100 billion in online sales since 1997.

Copyright © 2016 Miva, Inc - All Rights Reserved   Privacy Policy | Store Policy

Links
Contact Us
Receive Tips & Updates

Copyright © 2016 Miva, Inc - All Rights Reserved

Back To The Top