We got you!

Answers to your most common questions. Still have questions? 800-625-1670

  • How do I change my user password?

    You can change your user password at any time in the Merchant Interface.

    Step 1: Click User Profile in the main left side menu.
    Step 2: Click Change Password.
    Step 3: Enter your current password.
    Step 4: Enter a new password.
    Step 5: Re-enter the new password in the Confirm New Password text field.
    Step 6: Click Submit.

  • How do I charge a credit card outside of my website?

    You can easily submit charge transactions to the payment gateway.

    Step 1: Click Virtual Terminal in the main left side menu.

    Step 2: Select the Payment Method for the transaction that you need to enter: Charge a Credit Card or Refund a Credit Card. For a charge transaction, select Charge a Credit Card.

    Step 3: If you have chosen to charge a credit card, you must also select the Transaction Type. Three options are available: Authorize and Capture, Authorize Only, and Capture Only. If you select Authorize and Capture, the transaction will be sent for authorization and automatically submitted for settlement upon approval. If you select Authorize Only, the transaction will be sent for authorization but will not be automatically submitted for settlement. These transactions must be captured manually. If you select Capture Only, you must provide an authorization code. These transactions will be submitted for settlement.

    Step 4: Enter the credit card number and other associated details of the transaction. Required fields are marked with an asterisk (*).

    Step 5: Click Submit.

  • How do I refund a credit card?

    When submitting a transaction type of refund, the following rules apply:

    You can only refund a transaction that has been previously authorized or approved.

    The original transaction that you wish to refund must have a status of Settled Successfully. You may not issue refunds against unsettled, voided, declined or errored transactions.

    The refund transaction must be issued within 120 days of the date the original transaction was settled.

    A refund transaction cannot exceed the amount of the original transaction.
    The payment method provided in the refund transaction must match the payment method that was provided in the original transaction. You must provide the last four digits of the credit card number from the original transaction.

    Step 1: Click Virtual Terminal in the main left side menu.

    Step 2: Select the Payment Method for the transaction that you need to enter: Charge a Credit Card or Refund a Credit Card. For a refund transaction, select Refund a Credit Card.

    Step 3: Enter the details of the transaction, including the original Transaction ID in the Original Transaction ID text field. Other required fields are marked with an asterisk (*).

    Step 4: Click Submit.

  • How do I view my transactions?

    There are multiple ways to view transactions in the Merchant Interface.

    Perform a Transaction Search

    Step 1: Click Transactions in the main left side menu.

    Step 2: Enter your search criteria. You can view transactions within a date range, of a particular status, or for a specific customer or account number. Combine criteria to narrow your search.

    Step 3: Specify the number of results that you wish to view per page.

    Step 4: Click Search.

  • How do I run Transaction Reports.

    You can run a report to view a list of settled or declined transactions by settlement batch date.

    Step 1: Click Transaction Detail in the main left side menu.

    Step 2: Select an item type from the Item Type drop-down list. If you select Settled Transactions, you will view the complete list of transactions submitted for settlement in the selected settlement batch. If you select Declined Transactions, you will view the list of transactions within a settlement batch that were declined during authorization.

    Step 3: Select a settlement batch date from the Date drop-down list.

    Step 4: Click Run Report.

  • What is a transaction key?

    The payment gateway generated transaction key is a complex value that uniquely identifies a merchant’s payment gateway account, and is similar to an account password. Transaction keys are used to authenticate requests submitted to the payment gateway, and can be obtained in the Merchant Interface.

  • Authorize.Net Mobile Application

    Authorize.Net Mobile Application allows you to accept and manage credit and debit card payments securely with your Android (phones or tablets – OS 2.2 and higher) or Apple iOS Devices (iPhone, iPad or iPod touch – iOS 4.0 or later).

  • Why am I getting ‘error 13’ when checking out?

    You have either input the incorrect API or Transaction Key into the 3rd party solution or your Authorize.net account is inactive. Contact Moolah 800-625-1670

  • Why am I getting ‘line item 270 error’ when checking out?

    Line item 270 error is caused by your products in your shopping cart solution having quotes in the title ( example “Tshirt” ) .. Or your product title is over 31 characters in length.

    Remove all quotes in product titles and remain under 31 characters, including spaces.

  • Why am I getting ‘error code 87’?

    Error code 87 means that your Authorize.net account was set up for card present transactions versus e-commerce. Please call your Authorize.Net representative and ask them to setup your account for e-commerce transactions. Or call 800-625-1670.

  • Why am I getting ‘error Code 99’ ?

    Your API Login or Transaction key was entered into your 3rd party solution incorrectly, or your Authorize.net is not active. Call 800-625-1670

  • Why am I getting ‘Error 17 and Error 28’

    For a transaction to be authorized, your account at Moolah and with Authorize.Net must both be configured to accept the card type being submitted with the transaction (for example, American Express, Discover, etc.).

    To verify the card types that your Authorize.Net account currently accepts:

    Log into the Merchant Interface at https://account.authorize.net.
    Click Account from the main toolbar.
    Click Merchant Profile from the menu on the left.
    Under Payment Methods, review the card types listed.

    Next, contact us at Moolah ( 800-625-1670 ) so we can verify which card types are configured for your account. If we do not have your account configured for the card type you are attempting to process, we can assist with setting up the new card type.

  • How do I use the Address Verification Service (AVS)? What settings should I configure?

    The Address Verification Service (AVS) is a standard credit card verification feature supported by Authorize.Net that compares the billing address provided by a customer for a credit card transaction with the billing address on file for the cardholder at the credit card issuing bank. The issuing bank returns a code to the payment gateway indicating the results of the match. For example, the AVS code A indicates that the street address matched, but the first five digits of the ZIP code did not.

    The AVS filter settings in the Merchant Interface allow you to specify when a transaction should be rejected based on the results of the AVS match. The following result codes are possible:

    AVS CODE

    DESCRIPTION

    A – Address (street) matches, ZIP code does not

    B – Address information not provided for AVS check.

    E – AVS error

    G – Non-U.S. card issuing bank

    N – No match on address (street) or ZIP code

    P – AVS not applicable for this transaction

    R – Retry – System unavailable or timed out

    S – Service not supported by issuer

    U – Address information is unavailable

    W – 9 digit ZIP code matches, address (street) does not.

    Y – Address (street) and 5 digit ZIP code match

    Z – 5 digit ZIP matches, Address (Street) does not

    Note: AVS code X is also a valid response. This response indicates the Address (Street) and 9 digit ZIP match. The payment gateway cannot be configured to automatically reject AVS code X.

    AVS responses B, E, G, N, R, S, U are the default payment gateway AVS settings. When one of these AVS codes is returned, transactions are automatically rejected by the payment gateway unless you modify the default settings in the Merchant Interface.

    To configure transaction rejection settings based on the AVS response code:

    Log into the Merchant Interface at https://account.authorize.net/.

    Click Account from the main toolbar.

    Select Settings.

    Click Address Verification Service in the Security Settings section.

    Select the check box(es) next to the AVS codes for which the payment gateway should reject transactions.

    Click Submit.

    Note: In order to use AVS, you must require the billing address and ZIP code when collecting payment information from your customers. Please contact your Web developer or software provider to confirm that your credit card processing software requires this information.

    Tips for using AVS:

    AVS code N (neither the street address nor the ZIP code matches) is the most fundamental AVS check. If you implement only one AVS rejection setting, this should be it.
    If N is deselected, then the following settings should also be deselected: B, E, G, R, S, U. These responses mean that the address could not be verified by the card issuer. If you are not rejecting transactions when there is a legitimate AVS mismatch (N), then it is unnecessary to reject transactions that could not be verified with the issuer.

    To avoid errors when accepting prepaid debit cards or gift cards (stored-value cards with a Visa, MasterCard, Discover, or American Express logo), you will need to disable the U filter setting. For this type of transaction, the actual customer’s billing address often is not associated with the gift card, or does not exist on file at the issuing bank.

    Not all AVS checks from banks outside the United States will return G (the credit card issuing bank is of non-U.S. origin, and does not support AVS checks). Therefore, this is not an absolutely effective method for limiting transactions to the U.S.

    Code Y (both the street address and the first 5 digits of the ZIP code match) is the desired responses in most cases. This setting should never be selected for rejection.

  • How does Address Verification Service (AVS) work with International customers?

    The Address Verification Service (AVS) is used to validate the address that is on file with your customer’s credit card issuer for domestic transactions. However, in most cases, credit card institutions outside the U.S. do not support AVS. The result is that most international transactions cannot have their addresses verified. This puts these transactions at a higher risk of fraud. This also may result in higher discount rates from your Merchant Service Provider for accepting international transactions.*

    By default, the Authorize.Net gateway rejects these types of transactions. However, these settings can be altered so the majority of international transactions can be processed. To modify your AVS settings, please review the following instructions:

    Log into your Merchant Interface at https://account.authorize.net.

    Click Account from the main toolbar.

    Click Settings in the main left side menu.

    Click Address Verification Service.

    Unselect the check boxes for AVS Code G, U, and S to accept international credit cards.

    Click Submit to save the changes.

    Note: By changing these settings, you accept any risk associated with processing international transactions

Let's figure out your current rate.

You're going to need a recent statement from your current credit card processor.