Read our FAQ section for further information about our mail, phone & internet credit card accept and processing solutions.
     

FREQUENTLY ASKED QUESTIONS

Why should I submit my information & Get a Free Quote from You?

We know that if you give us the opportunity to show you what we can do for your business, you'll love our products and pricing. Just as importantly, you'll have all the tools you'll need to feel comfortable with your decision to make us the partner you can count on for all of your current and future processing needs.


If you're looking for a processor with low rates and no long-term contracts, cancelation fees or set- up fees, NoblePay is the obvious choice. Click here to gain access to all of our affordable solutions, product demonstrations and downloadable product brochures.

There is plenty of competition within the bankcard industry. Unfortunately, many providers use “smoke and mirrors” to make their costs appear lower than they actually are.

Did you know that many processors use teaser rates or quote select card types to make their rates appear lower than they really are, then charge more in another area to make up for it?

For example, you may see rate quotes that look exceedingly attractive. What is not readily disclosed, however, are a myriad of additional items, such as dues and assessments or rewards surcharges, that offset any savings you may have obtained from the lower rate. These hidden charges make the cost of their seemingly low rate offer much higher than what you'll enjoy with NoblePay.

Our staff has been serving merchants for over 14 years. We don't need to resort to sleight of hand techniques because we’ve always offered extremely competitive rates and fees. We pride ourselves on not just earning your business, but earning your trust.
What are your rates?
We have some of the very best rates you'll find anywhere, guaranteed. Rates are determined by your card acceptance method. For example, a traditional brick and mortar store is able to swipe the card and obtain a signature at the time of the sale, which is known as a card- present sale. An order taken over the phone or via the Internet is considered a card- not- present sale. To see our Rates click here.
Why can't I just use my friend's merchant account?
Using another company’s merchant account is called factoring or "credit card laundering" and is a violation of Visa and MasterCard regulations. Factoring can result in  fines to you and the loss of the merchant account of the person who allowed you to use their account.
How long does it take to receive money after I run a card?
All funds are electronically deposited into your checking account and are available within 24-48 hours.

How long does it take to setup a new account?
Setting up an account is quick and easy! You can often be approved on the day you apply, and in most cases, we can have you up and running within 24-48 hours. To get started use our secure online application

Is there a contract or termination fee?
At NoblePay, we don’t believe in long-term contracts. We  offer an extremely competitive program with superior service, so you’ll have no reason to look anywhere else. If you do decide to cancel for any reason, however, you can do so at any time. Just give us 30 days notice and you won't be charged an early termination fee.
Why should I use your service instead of PayPal?

PayPal is great for small, hobby type businesses or for individuals who want to transfer funds online. There are no monthly fees, but the rates are very high. Also, accessing your money can be a challenge because it’s not electronically deposited into you account, like a true merchant account. Instead, you need to manually request the transfer. Once that’s done, it can take 4 or more days for the funds to be deposited into your account. Having to manually request the funds transfer is time consuming and can cause cash flow challenges.

PayPal isn't transparent to the user, and won't allow you to promote your brand to your customer. Instead, you're forced to promote PayPal's brand, which can give you a less than professional image.  If your company has grown to the point where it’s become a serious business, then PayPal comes up short.

How do I apply for a new account and what are the criteria for getting approved?
We typically approve 99% all sole proprietor, corporation, LLC & non-profit applicants. You can see the required data for applying at our secure online application HERE. The same fiduciary information you supplied when you established a bank account will be required when applying for a merchant account. As long as you have no recent bankruptcies, outstanding delinquencies or are not listed on a Terminated Merchant File (TMF) we can get you approved.
Do you offer a free terminal program?

No, and here’s why. The old adage “You can’t get something for nothing” was never more applicable than with so- called “free terminal” programs. In this instance, “free” actually means no upfront costs.
What competitors often do is provide a merchant with a credit card terminal at no upfront cost but then charge other fees instead, such as an annual fee, a monthly minimum fee or a termination fee.
Also, you never technically own the terminal. Rather, it’s yours to use only for as long as you maintain your processing relationship with that company. In fact, the terminal is programmed in a manner that prohibits you from taking it to another service provider.

Should you decide to cancel your account, the agreement will usually specify that you return the equipment in the same condition as it was received. Of course, the definition of “same condition” is subjective, and returning equipment in flawless condition after it’s been in continual use is often impossible. The penalty for violation of this provision is usually between $595 and $795, which hardly makes it a free terminal!

The bottom line is that the excessive hidden fees and penalties free terminal providers levy make the costs of these programs far higher than meets the eye. At NoblePay, we don’t believe such practices form the foundation for building lasting partnerships with our merchants.
What are rewards cards?

A full 60% of the credit cards issued in the United States today are rewards cards. Rewards cards have been designed by banks to give cardholders discounts and other perks in an effort to incent them to use their cards more often, and for larger dollar amounts. As this card category grows in popularity, merchants will be seeing charges from rewards cards more and more often on their monthly credit card processing statements.
The good thing about rewards cards is that consumers are using them in greater numbers, which mean more sales volume. The bad thing is that it’s more expensive to process these types of cards, which means merchants are forced to pay higher rates than necessary by some card processors.
One of the most common misunderstandings between merchants and card processors is related to the  discount rate. When you look for a merchant account you’re quoted a base rate, such as 1.69% for card- present and 2.24% for card- not- present transactions. What isn’t usually discussed is the rate you’ll be charged for other card types, such as rewards cards and business cards.
Most processors have a three- tier system, which means the card- not- present rate will be applicable for most rewards cards. However, if you’re primarily a card- not- present merchant, some providers will initiate a rewards- based surcharge, which can be as much as 1 - 1.9% above the base rate. Some even tack on .09-.13 cents per transaction as an additional fee.

At NoblePay, all rewards cards fall to the card- not- present rate, with NO rewards- based surcharges or additional fees of any type.

Larger processing merchants may qualify for a lower rewards.

BACK

 

 

 

 

 

 

 

 

 


RISK MANAGEMENT FAQ'S

PowerPay is committed to helping you to control and prevent fraud. With the growth of e-commerce and the rise of identify theft, fraud prevention has never

'been as critical. It is not just e-commerce and mail order transactions that require extra diligence. Face to face transactions are also subject to continuing fraud attempts.

Scam artists are more savvy than ever before and understand the latest security features that Visa and MasterCard are creating to control this problem. Merchants must be alert and take extra precautions wherever possible, because they are financially responsible for fraudulent transactions, including those approved by the bank that issues the consumer’s credit card.

Through the accompanying documents and links, we hope to provide the basic information you will need to help prevent fraud from occurring in your business.

Chargeback Process
Preventing Chargebacks
12 potential signs of Card Not Present Fraud
Visa-MasterCard Card Not Present fraud prevention tools

Additional Fraud Management and e-Commerce Resources
Verified by Visa Learn about the Verified by Visa program to combat e-commerce fraud

Visa E-Commerce Merchants’ Guide to Risk Management
Visa E-Commerce Merchants’ Guide to Risk Management (E-Commerce)
Visa Card Not Present
Merchant Requirements for Securing Cardholder Information
Electronic Commerce Security Architecture Best Practices
 
Visa/MasterCard Terminal Response Codes
Response Action
Approved Ask the customer to sign the sales receipt.
Declined Return the card to customer and ask for another Visa card.
Call or Call Center Call your voice authorization center and tell the operator that you have a "Call" or "Call Center" response. Follow the operator instructions.

Note: In most cases, a "Call" or "Call Center" message just means the card Issuer needs some additional information before the transaction can be approved.
Pick Up Keep the card if you can do so peacefully.
No Match Swipe the card and re-key the last four digits. If "no match" response appears again, keep the card if you can do so peacefully. Request a Code 10 authorization.


Chargeback Process

Introduction to the Chargeback Process
Chargeback Details
First Chargeback Phase
First Reversal Phase
Second Chargeback and Second Reversal Phase (MasterCard only)
Issuing Bank Pre-Arbitration Phase (Visa only)
 

Introduction to the Chargeback Process

BACK


III. Second Chargeback and Second Reversal Phase (MasterCard only):

Once a Reversal (and the subsequent debit) is received back at the Issuing Bank, they will then forward the “Merchant’s Letter" back to their Cardholder for a response. If the Cardholder wishes to pursue the dispute further, they then send in a “Rebuttal Letter" back to the Issuing Bank and if the Issuing Bank feels that their response is valid, will submit a Second Chargeback. A Second Chargeback functions just like a First Chargeback, except a Chargeback fee is not assessed and the disputed amounted is immediately debited out of the Merchant’s business checking account. The Merchant is sent another letter explaining what, if any, documentation is required to pursue this dispute further. This “Second Chargeback" phase of the dispute is then considered “Resolved to the Merchant" and will remain closed until the Merchant responds back to the letter sent to them. If the Merchant does indeed respond to the letter sent to them a ‘"Second Reversal" phase of the dispute is opened. An Acquirer Chargeback Analyst will then review the letter and one of two scenarios will occur:

1.  If the Chargeback Analyst deems the Merchant’s response as invalid, they will close out this phase as “Request Denied" and will mail a letter to the Merchant explaining why the Chargeback cannot be pursued further at that time.
   
2.  If the Chargeback Analyst deems the Merchant’s response as valid, they will submit a “Pre-Arbitration" letter directly to the Issuing back advising that the Acquirer believes the Merchant’s claim is valid and that Acquirer will request MasterCard to make an Arbitration ruling on the dispute if the Issuer disagrees with the Merchant’s claim.
   
 
a.  If the Issuing Bank agrees with the Merchant’s claim, they will simply forward the funds back to the Acquirer and the Acquirer will then credit the Merchant’s business checking account accordingly. The dispute at this point is considered “Successful" and cannot be re-opened.
   
b.  b. If the Issuing Bank disagrees with the Merchant’s claim, they will send a letter back to the Acquirer advising of such. The Acquirer will then send a form to the Merchant requesting that they sign the form which makes the Merchant liable for Arbitration filing fees. (When MasterCard makes an Arbitration ruling, it assesses a $400.00 filing fee to the loser of the dispute) If the Merchant does not agree to the fees, the Acquirer simply closes out the Second Reversal phase of the case as “Unsuccessful". If the Merchant does indeed agree to the fees and submits the signed form, the Acquirer then submits an Arbitration Request to MasterCard directly.
 
i.  If MasterCard rules in the Merchant’s favor, the Issuer is immediately debited and the Acquirer is credited for the amount in dispute and forwards the credit to the Merchant’s business checking account. The Issuing Bank is also assessed the $400.00 in filing fees and the Acquirer closes this phase of the dispute as “Successful"
   
ii.  If MasterCard rules in the Merchant’s favor, the Issuer is immediately debited and the Acquirer is credited for the amount in dispute and forwards the credit to the Merchant’s business checking account. The Issuing Bank is also assessed the $400.00 in filing fees and the Acquirer closes this phase of the dispute as “Successful"

BACK


IV. Issuing Bank Pre-Arbitration Phase (Visa only):

Once a Reversal (and the subsequent debit) is received back at the Issuing Bank, they will then forward the “Merchant’s Letter" back to their Cardholder for a response. If the Cardholder wishes to pursue the dispute further, they then send in a “Rebuttal Letter" back to the Issuing Bank and if the Issuing Bank feels that their response is valid, will submit a “Pre-Arbitration" letter directly to the Acquirer advising that they feel that their Cardholder’s claim is valid that they will request Visa make an Arbitration ruling on the dispute if the Acquirer disagrees with the Cardholder’s claim. The Merchant is then sent another letter along with the Cardholder’s rebuttal advising that they need to respond within 10 days. If the Merchant does not respond to the letter within the specified timeframes, the Acquirer Chargeback Analyst will credit the Issuing Bank back for the disputed amount and in turn debit the Merchant’s business checking account. This phase of the dispute will then be closed as “Unsuccessful". If the merchant does indeed respond within the specified timeframe, one of two scenarios will occur:

1.  If the Chargeback Analyst deems the Merchant’s response as invalid, they will close out this phase as “Request Denied" and will credit the Issuing Bank back for the disputed amount and in turn debit the Merchant’s business checking account. The Chargebacks Analyst will also mail a letter to the Merchant advising of the debit and will also explain why the Chargeback cannot be pursued further at that time.
   
2.  If the Chargeback Analyst deems the Merchant’s response as valid, the Acquirer will then send a form to the Merchant requesting that they sign the form which makes the Merchant liable for Arbitration filing fees. (When Visa makes an Arbitration ruling, it assesses a $400.00 filing fee to the loser of the dispute) If the Merchant does not agree to the fees, the Acquirer simply closes out the Pre-Arbitration phase of the case as “Unsuccessful" and will credit the Issuing Bank back for the disputed amount and in turn debit the Merchant’s business checking account. If the Merchant does indeed agree to the fees and submits the signed form, the Acquirer then responds to the Issuing Bank advising them that they do not agree with the Cardholder’s claim. The Issuing bank then submits an Arbitration Request directly to Visa.
a.  If Visa rules in the Merchant’s favor, all funds remain where they are and in addition, The Issuing Bank is assessed the $400.00 in filing fees. The Acquirer then closes this phase of the dispute as “Successful"
   
b.  If Visa rules in the Issuing Bank’s favor, they are immediately credited for the amount in dispute and the Acquirer is immediately debited for the same amount and in turn this amount is immediately debited from the Merchant’s business checking account along with the $400.00 in filing fees. The Acquirer then closes this phase of the dispute as “Unsuccessful"

BACK


Preventing Chargebacks

Most chargeback situations arise at the point of transaction—at the time the transaction is completed—and most can be prevented with a little training.

Consider these tips to avoid potential chargebacks...

Card Present Transactions
   
Card-not present Transactions

Card Present Transactions
1.  Do not complete a transaction if the authorization request was declined. Do not repeat the authorization request after receiving a decline.
   
2.  If you receive a “Call" message in response to an authorization request, call your authorization center. Be prepared to answer questions. The operator may ask to speak with the cardholder. If approved, write the authorization code on the sales receipt. If declined, ask the cardholder for another Visa card.
   
3.  Make an imprint for all card-present transactions. If you have a point-of-sale terminal with a magnetic-stripe reader, swipe the card through the reader for every face-to-face transaction. If the terminal isn’t working or a card’s magnetic stripe cannot be read, key-enter the account information and make an imprint of the embossed information onto the sales receipt using a manual imprinter. Even if the transaction is authorized and the cardholder signs the receipt, if the receipt does not have an imprint of the embossed account number and expiration date, the transaction may be charged back to you for “no imprint" if the cardholder later denies participating in the transaction.
   
4.  Obtain cardholder signature. The cardholder’s signature on card-present transactions is required. Failure to obtain the cardholder’s signature could result in a chargeback for “no signature" if the cardholder denies authorizing or participating in the transaction. Always compare the signature on the sales slip and the signature on the back of the card. If the card does not carry any signature, ask the customer to show you a picture ID, and have him sign the card at the time of purchase.
   
5.  Make only one imprint of the card for each transaction. Making more than one imprint can lead to duplicate deposits and increase the chance of a chargeback. If you need to redo a sales receipt because of an error, write “VOID" across the incorrect sales receipt, inform the cardholder, and tear up the incorrect sales receipt in view of the customer.
   
6.  Ensure that transactions are entered into point-of-sale terminals only once—and deposited only once. Entering the same transaction into a terminal more than once, or depositing both the merchant copy and the bank copy of the sales receipt with your acquirer, or depositing the same transaction with more than one merchant bank can all result in “duplicate transaction" chargebacks.
   
7.  Ensure that incorrect sale receipts are voided and that transactions are processed only once.
   
8.  If your establishment has policies regarding merchandise returns, refunds, or service cancellation, disclose these policies to the cardholder at the time of the transaction. Your policy should be pre-printed on your sales receipts within ¼ inch of cardholder’s signature; if not, write or stamp your refund/return policy information on the sales receipt near the customer signature line before the customer signs (be sure the policy shows clearly on all copies of the sales receipt). Failure to disclose such policies at the time of the transaction will be to your disadvantage should the customer return the merchandise.
   
9.  Deposit sales receipts with your merchant bank as quickly as possible, preferably within one to five days of the transaction date—do not hold on to them. Failure to deposit in a timely manner can result in chargebacks for “late presentment."
   
10.  Deposit credit receipts with your acquirer as quickly as possible, preferably the same day as the credit transaction is generated. Failure to process credits in a timely manner can result in chargebacks for "credit not issued."
   
11.  Keep customers informed on the status of their transactions.
   
12.  If the merchandise or service to be provided to the cardholder will be delayed, advise the cardholder in writing of the delay and the new expected delivery or service date.
   
13.  If the merchandise ordered by the cardholder is out of stock and delivery will be delayed or this item is no longer available, advise the cardholder in writing and offer the cardholder the option of purchasing a similar item or canceling the transaction. Do not substitute another item unless the customer agrees to accept it. By giving the customer notice and the option to cancel, you may help avoid a customer dispute regarding the merchandise and a possible chargeback.
   
14.  Ship merchandise before depositing transaction. Don’t deposit transactions with your merchant bank until you have shipped the related merchandise. If customers see a transaction on their monthly Visa statement before they receive the merchandise, it could lead to a preventable chargeback.
   
15.  When refunding a customer, always credit the same card that was used for the corresponding sale.
   
16.  Respond to all sales draft requests. Should you receive a request for copy of sales draft, respond immediately. Failure to send in copy will result in a chargeback with no representment rights
   
17.  Change printer ribbon frequently- illegible sales drafts can also initiate chargebacks.

BACK


Card-not present Transactions:

1.  Do not complete a transaction if the authorization request was declined. Do not repeat the authorization request after receiving a decline.
   
2.  If a customer requests cancellation of a recurring transaction which is billed periodically (monthly, quarterly, annually), always respond to the request and cancel the transaction immediately or as specified by the customer. As a customer service, advise the customer in writing that the service, subscription, or membership has been cancelled and state the effective date of the cancellation. Failure to respond to customer cancellation requests almost always leads to chargebacks.
   
3.  If the merchandise or the service to be provided to the cardholder will be delayed, advise the cardholder in writing (e-mail for e-commerce merchants) of the delay and the new expected delivery or service date. Also, if the item is out of stock or no longer available, offer the cardholder the option of purchasing a similar item or canceling the transaction. Do not substitute another item unless the customer agrees to accept it. By giving the customer notice and the option to cancel, you may help avoid a possible chargeback
   
4.  Ship merchandise before depositing transaction. Don’t deposit transactions with your merchant bank until you are about to or have shipped the related merchandise. If customers see a transaction on their monthly Visa statement before they receive the merchandise, it could lead to a preventable chargeback.
   
5.  When refunding a customer, always credit the same card that was used for the corresponding sale. Do not offer a check or other form of payment in place of a refund.
   
6.  Use the Address Verification tool (AVS) and require a perfect match on cardholder’s billing address. Partial AVS match will not stand in a “non authorization" chargeback scenario. If you need assistance in setting the AVS properly on your Gateway, contact your payment gateway provider or the Loss Prevention department of your credit card Processor for assistance.
   
7.  Make sure the billing and the shipping address are the same. If not, make sure you verify the shipping address. You can search through the Yellow-White pages, ask for a copy of a utility bill, or a copy of a Driver’s License to validate the shipping address. You can also ask the customer to call the Issuer and add the new address to the billing information
   
8.  Obtain and verify the Card Code (CVV2/CVC2). This is the 3-4 digits number on the back of your card (on the front for American Express). This information can be captured only if your shopping cart, and your gateway are set up for it. Please, contact your webmaster and/or Gateway provider for details.
   
9.  Cancellation/Return Policy needs to be acknowledged by cardholder. Policy needs to be acknowledged by the customer. For telephone or mail order merchants, policy must be acknowledged with a signature on the order form, contract, or invoice. For e-commerce merchants, policy can be incorporated in the online Terms and Conditions of the sale, and require the cardholder to click on an “I agree" button before completing the order.
   
10.  Generate an RMA number for submitted cancellations.
   
11.  Obtain signed proof of delivery. Tracking numbers without a signature are not considered valid proof of delivery.
   
12.  Verify the Internet Protocol (IP) address. Even though the IP verification is not a 100% guarantee, adding this feature will help you detect fraud. Your Gateway provider and/or other software vendor should be able to help you get started with this validation process. There is a variety of IP validation software that can be downloaded at no cost.

BACK


12 potential signs of Card Not Present Fraud

Keep your eyes open for the following fraud indicators. When more than one is true during a card-not-present transaction, fraud might be involved. Follow up, just in case.

1.  First-time shopper: Criminals are always looking for new victims.
   
2.  Larger-than-normal orders: Because stolen cards or account numbers have a limited life span, fraudsters need to maximize the size of their purchase.
   
3.  Orders that include several of the same items: Having multiples of the same item increases a criminal's profits.
   
4.  Orders made up of “big-ticket" items: These items have maximum resale value and therefore maximum profit potential.
   
5.  “Rush" or “overnight" shipping: Crooks want these fraudulently obtained items as soon as possible for the quickest possible resale, and aren’t concerned about extra delivery charges.
   
6.  Shipping to an international address: A significant number of fraudulent transactions are shipped to fraudulent cardholders outside of the U.S. Visa/MC address verification (AVS) can't validate non-U.S., except in Canada and the United Kingdom or few other banks who participate in the US AVS program.
   
7.  Transactions with similar card account numbers: Particularly useful if the account numbers used have been generated using software available on the Internet.
   
8.  Shipping to a single address, but transactions placed on multiple cards: Could involve an account number generated using special software, or even a batch of stolen cards.
   
9.  Multiple transactions on one card over a very short period of time: Could be an attempt to "run a card" until the account is closed.
   
10.  Multiple transactions on one card or a similar card with a single billing address, but multiple shipping addresses: Could represent organized activity, rather than one individual at work.
   
11.  In online transactions, multiple cards used from a single IP (Internet Protocol) address: More than one or two cards could definitely indicate a fraud scheme.
   
12.  Orders from Internet addresses that make use of free e-mail services: These e-mail services involve no billing relationships, and often neither an audit trail nor verification that a legitimate cardholder has opened the account.

BACK


Visa – MasterCard Card Not Present fraud prevention tools

Appropriate preventive action can help reduce fraudulent transactions and potential customer disputes. Make use of these Visa tools and controls to verify the legitimacy of the Visa cardholder and the card in every card-not-present transaction.

Tool Description
Address Verification Service (AVS) Allows card-not-present merchants to check a cardholder’s billing address with the card Issuer. The merchant includes an AVS request as part of the authorization and receives a result code indicating whether the address given by the cardholder matches the address on file with the Issuer.
Card CodeVerification (CVV2- CVC2) This is a three-digit number imprinted on the signature panel of Visa-MasterCard cards to help card-not-present merchants verify that the customer has a legitimate card in hand at the time of the order. The merchant asks the customer for the card code and then sends it to the card Issuer as part of the authorization request. The card Issuer checks the card code to determine its validity, then sends a result back to the merchant along with the authorization.
Verified by Visa (VbV) Enables e-commerce merchants validate a cardholder's ownership of an account in real-time during an online Visa card transaction. When the cardholder clicks "buy" at the checkout of a participating merchant, the merchant server recognizes the registered Visa card and the “Verified by Visa" screen automatically appears on the cardholder’s desktop. The cardholder enters a password to verify his or her identity and the Visa card. The Issuer then confirms the cardholder’s identity.
MasterCard SecureCode MasterCard enables e-commerce merchants to actually validate that a MasterCard cardholder is authorized to use the card and qualify the transaction for a guaranteed payment that protects against cardholder unauthorized chargebacks.

MasterCard SecureCode runs on your website and interacts with both the customer and their card Issuer. When your customer is checking out, a simple pop-up box appears asking them to enter a private code that has been registered with their bank.

Their bank then validates that code and provides you with a means of achieving a fully guaranteed transaction. For more information, visit http://www.mastercardmerchant.com

AUTHORIZE.NET FAQ

What is Authorize.Net?
What is a payment gateway?
What does Authorize.Net do?
What services and products does Authorize.Net provide?
What type of merchants use Authorize.Net?
Where does Authorize.Net fit in the credit card payments process?
What credit cards does Authorize.Net support?
How secure is submitting transactions over the Internet?
Does Authorize.Net store customer payment information?
How secure is Authorize.Net?
What is Secure Sockets Layer (SSL)?
What does Internet Protocol (IP) mean?
What does Authorize.Net do to protect merchants from fraud?
How do I connect my Web site to Authorize.Net?
Can Authorize.Net process my point-of-sale (POS) transactions?
I want to process transactions via IP from my retail store, how do I get started?
I already have an Authorize.Net Payment Gateway account for processing transactions online, do I need another one to be able to process retail transactions using Authorize.Net?
What is a merchant bank account?
What does an Authorize.Net Payment Gateway account include?
What is the Merchant Interface?
What is the Virtual Terminal?
What is Batch Upload?
What is eCheck.Net®? How do I sign up for it?
What is Automated Recurring Billing™ (ARB)?
What is Fraud Detection Suite™ (FDS)?
What processors does Authorize.Net support?



What is Authorize.Net?
Authorize.Net is the preferred payment gateway among resellers and merchants for managing payment transactions using the power and speed of the Internet. Authorize.Net also provides other business enhancing products that help merchants manage their transactions.

BACK


What is a payment gateway?

A payment gateway is a complex system of computer technologies and processes that allow merchants to electronically submit payment transactions to the payment processing networks (i.e., the Credit Card Interchange and the Automated Clearing House Network) via the Internet. More specifically, payment gateways provide the necessary Internet infrastructure that enables merchants to accept credit card and electronic check payments from Web sites.

BACK


What does Authorize.Net do?

Authorize.Net facilitates the submission and routing of credit card and eCheck.Net® payment transactions on behalf of its client merchants to the processing networks in real-time—24 hours a day, seven days a week. The Authorize.Net Payment Gateway supports all types of merchant business models, including: from Web sites, at retail (physical locations where payment is presented directly to the merchant by the customer at the time of purchase), mail order/telephone order (MOTO) call and fulfillment centers, and from wireless devices.

Authorize.Net also provides merchants with business and transaction enhancing products, such as eCheck.Net®, Automated Recurring Billing™, and Fraud Detection Suite™.

BACK


What services and products does Authorize.Net provide?
Primarily, Authorize.Net provides payment gateway or IP payment processing services to Web sites, retail (physical location where payment is presented directly to the merchant by the customer at the time of purchase), MOTO, and mobile merchants.

Authorize.Net also provides other value adding payment processing products that help merchants enhance transaction processing, streamline their business, and save time and money. Some of Authorize.Net’s value-products are: Automated Recurring Billing™ (ARB), Fraud Detection Suite™, and support for Verified by Visa and MasterCard® SecureCode™. In addition, Authorize.Net offers an exclusive electronic check payment option, eCheck.Net®.

BACK


What type of merchants use Authorize.Net?
The Authorize.Net Payment Gateway supports all types of merchant business models, including: from Web sites, at retail (physical locations where payment is presented directly to the merchant by the customer at the time of purchase), mail order/telephone order (MOTO) call and fulfillment centers, and from wireless devices for mobile merchants.

BACK


Where does Authorize.Net fit in the credit card payments process?
In the credit card payments process, Authorize.Net sits between the merchant and the payment processing entity (e.g., FDMS, TSYS Acquiring Solutions (SM), Global) that does business with the merchant’s bank. Authorize.Net also has a relationship with the payment processing entity, which allows Authorize.Net to pass transaction information on behalf of the merchant via the Internet (over a proprietary and secure connection).

A typical Authorize.Net credit card transaction flows in the following way:

  1. A credit card transaction is submitted to the Authorize.Net Payment Gateway either from a merchant Web site or directly from a merchant.

  2. Authorize.Net automatically passes the transaction to the Acquiring Bank’s Processor (the payment processor that does business with the merchant’s bank).

  3. The Acquiring Bank’s Processor passes the transaction to the Credit Card Interchange System (an entity that routes payment information to the parties involved in settling a credit card transaction).

  4. The Credit Card Interchange System routes the transaction to the appropriate Credit Card Issuer (the bank or organization that issued the customer their credit card).

  5. The Credit Card Issuer approves or declines the transaction and passes both the transaction results and the appropriate funds back through the Credit Card Interchange System.

  6. The Credit Card Interchange System relays the transaction results to the Acquiring Bank’s Processor.

  7. The Acquiring Bank’s Processor relays the transaction results to Authorize.Net.

  8. Authorize.Net stores the transaction results and sends it back to the merchant and customer.

  9. The Credit Card Interchange System also passes the appropriate funds for the transaction to the Acquiring Bank (the merchant’s bank).

  10. The Acquiring Bank passes remaining funds to the merchant’s bank account.

On average, steps 1-8 take only 3 to 4 seconds!

BACK


What credit cards does Authorize.Net support?
Authorize.Net supports all major credit cards: Visa, MasterCard, Discover, American Express, Japan Credit Bureau (JCB), Diner’s Club. Authorize.Net also has an exclusive electronic check solution, eCheck.Net®.

BACK


How secure is submitting transactions over the Internet?
Submitting transactions over the Internet can be as secure as providing credit card or check payments in person. All parties involved with processing any payment transaction—including customers, merchants, merchant service providers or businesses that handle customer payment information, and payment gateways—should be vigilant about protecting customer payment information.

For merchants and merchant service providers that may handle customer payment information, there are many payments industry security initiatives and programs in place that are designed to safeguard customer payment and other sensitive information—programs with which in many cases they are required to prove compliance. As you seek merchant service providers to work with, be sure to find out about their efforts to meet industry standard security requirements and practices. A professional organization will do everything in their capacity to meet and maintain the highest levels of Internet security—which is why Authorize.Net is compliant with maintaining the highest industry security standards.

BACK


Does Authorize.Net store customer payment information?
For the purpose of risk management and to be able to process certain types of subsequent transactions (e.g., recurring billing, refunds), yes, Authorize.Net will store customer payment information in a highly secured database for a limited period of time. However, all sensitive or personally identifying customer information that is stored by Authorize.Net is masked in the Merchant Interface and in merchant reporting. In addition, in order to maintain compliance with several card association regulated security compliance programs, internal access to customer information is highly restricted.

Once customer payment information has been stored for 120 days (from the date it was originally received), the Authorize.Net purges the full information and stores only masked information.

BACK


How secure is Authorize.Net?

Authorize.Net is uncompromising when it comes to providing merchants with secure, trustworthy payment processing services. For receiving and transmitting customer payment information Authorize.Net implements the most advanced Internet security protocols including 128-bit Secure Sockets Layer (SSL). On top of that, Authorize.Net consistently employs an extensive number of strong practices, procedures and industry leading technologies to maintain tight security for the entire payment gateway platform. We also maintain compliance with high quality security programs developed by the card associations, such as Visa Cardholder Information Security Program (CISP) and MasterCard Site Data Protection (SDP); and are continually investing time and money to maximize the security surrounding the payment gateway.

BACK


What is Secure Sockets Layer (SSL)?
Secure Sockets Layer (SSL) is an Internet protocol that safeguards electronic communications between two or more computers. For a communication or transaction that is transmitted over an “end to end" SSL connection, the computer initiating the transmission will open an SSL connection. This means that when Computer A sends a request to Computer B to transmit information, Computer A will include a digital certificate—a complex authentication tool that is basically a third-party issued certification that Computer A is a trustworthy source. Computer B then accepts the transmission and, in the event that Computer B has information to return to computer A, the SSL connection may remain open until the transaction between the two computers is complete.

Server-side SSL can also be used in the event that Computer A doesn’t have the necessary digital certificate or the ability to open an SSL connection to submit a communication to Computer B. However, Computer B may have some other means of authenticating the trustworthiness of Computer A or other computers that are submitting communication requests. Any transmissions sent to other computers by computer B will be transmitted via an SSL connection to those computers. In this case, the SSL connection is terminated once Computer B has completed its transmission.

When transmissions are sent over an SSL connection, they cannot be intercepted, viewed or modified by other parties on the Internet. As such, customer payment information is transmitted securely.

BACK


What does Internet Protocol (IP) mean?
Internet Protocol (IP) is the method of transmitting information and communications between computer systems and networks via the Internet. For the payments industry, the ability to use IP to transmit customer payment information directly to the processing network has revolutionized the way merchants run business—opening doors to a wide range of new payments acceptance opportunities, including from Web sites and wireless devices, to helping store-front merchants cut costs and speed up checkout lines.

BACK


What does Authorize.Net do to protect merchants from fraud?
Authorize.Net recognizes that fraud may well be the biggest challenge facing our merchants—which is why helping merchants protect themselves from fraud is one of our highest priorities. There are several ways Authorize.Net protects merchants from fraud:

  • Unlike other payment gateways, Address Verification Service (AVS) and Card Code Verification (CCV) tools come with our standard payment gateway accounts—helping merchants build their fraud protection program from the ground up.

  • Authorize.Net has an established and dedicated Fraud Management Department, dedicated to the daily monitoring of merchant accounts and development of merchant protection practices and program.

  • Based on extensive research and criteria developed by our dedicated Fraud Management Department, the Authorize.Net Fraud Detection Suite (FDS) provides an unrivaled set of transaction filters and tools that empower merchants to identify, prevent and manage potentially fraudulent transactions.

Authorize.Net is continually investing money and resources into providing merchants with the tools and information they need to protect themselves from fraud.

BACK


How do I connect my Web site to Authorize.Net?
Connecting your Web site to the Authorize.Net Payment Gateway requires some additional code and development for your Web site. To do this, you will need to make arrangements with your company’s Web developer or a contracted Web developer. See the Auhthorize.net Connection Methods page for more information about our secure connection methods. Your Web developer may be able to help you choose the connection method that is right for your business.

BACK


Can Authorize.Net process my point-of-sale (POS) transactions?
Yes! Retail merchants can harness the power and speed of the Internet to submit payment transactions, cutting costs and speeding up checkout lines. Authorize.Net offers a variety of POS solutions for all types of retail merchants through our partner POS solutions providers. In fact, many of our partner POS solutions providers offer POS hardware and software that is already integrated to the Authorize.Net Payment Gateway.

BACK


I want to process transactions via IP from my retail store, how do I get started?
To process your retail transactions via the Authorize.Net Payment Gateway, you will need an Authorize.Net Card Present Payment Gateway account, and a Card Present merchant bank account (a type of bank account that allows you to collect proceeds from retail transactions). To obtain these services, you can choose one of many of our partner point of sale (POS) solutions providers.

Many of our partner POS solutions providers offer POS hardware and software that is already integrated to the Authorize.Net Payment Gateway. If you would like more information about what is necessary to integrate directly to the Authorize.Net Payment Gateway yourself, please see the Authorize.net Card Present Implementation Guide.

BACK


I already have an Authorize.Net Payment Gateway account for processing transactions online—do I need another one to be able to process retail transactions using Authorize.Net?
Yes, you will need a separate Authorize.Net Card Present payment gateway account.

BACK


What is a merchant bank account?
A merchant bank account is a type of financial institution or bank account that allows merchants to collect proceeds from consumer bank account or credit card payment transactions. A Card Present (CP) merchant account is used by merchants that process IP transactions received at a physical location, where payment is physically presented to the merchant by the customer at the time of the transaction. A Card Not Present (CNP) merchant account is used by merchants that receive payments electronically or in situations where payment is not physically presented to the merchant by the consumer at the time of the transaction.

BACK


What does an Authorize.Net Payment Gateway account include?
A standard Authorize.Net Payment Gateway account includes the following:

  • Connection Methods – Several options including AIM, SIM and Card Present.

  • Merchant Interface – A password-protected Web site that allows merchants to manage transactions, change security and account settings, and generate reports.

  • Virtual Terminal – Included in the Merchant Interface, the Virtual Terminal allows merchants to manually key in and submit transactions easily and quickly.

  • Batch Upload – Included in the Merchant Interface, the Batch Upload feature allows merchants to upload multiple transaction at once and facilitates uploads from a spreadsheet or proprietary business application.

  • Address Verification Service (AVS) – A fraud prevention tool that allows merchants to filter transactions that are submitted with billing addresses that do not match the cardholder’s billing address on file at the card issuing bank.

  • Card Code Verification (CCV) – A fraud prevention tool that allows merchants to filter transactions that are submitted with a card code that does not match the cardholder’s card code on file at the issuing bank.

  • Free Customer Support – Authorize.Net provides live technical and account support seven days a week, as well as access to online documentation and user guides.

BACK


What is the Merchant Interface?

The Merchant Interface is a password-protected Authorize.Net Web site that allows merchants to manage transactions, change security and account settings, generate reports, and sign up for value-adding products.

BACK


What is the Virtual Terminal?
The Virtual Terminal is a feature of the Merchant Interface that allows merchants to manually key in and submit transactions easily and quickly.

BACK


What is Batch Upload?
Batch Upload is a feature of the Merchant Interface that allows merchants to upload multiple transactions at a time from a spreadsheet or proprietary business application.

BACK


What is eCheck.Net®? How do I sign up for it?
Authorize.Net’s exclusive electronic check payment solution. eCheck.Net® allows merchants to post charge and refund transactions directly to a customer’s bank account from their Web site. For merchants already processing credit card transactions using Authorize.Net, using eCheck.Net is easy. Authorize.Net provides combined transaction management, reporting and customer support.

BACK


What is Automated Recurring Billing™ (ARB)?
ARB is an Authorize.Net value-add product that allows Web and MOTO merchants to create a recurring billing schedule or “subscription" for the purchase of goods or services. Merchants enter transactions and customer billing information, specify a billing amount and billing interval and ARB does the rest—automatically generating subsequent transactions for the duration of the subscription.


What is Fraud Detection Suite™ (FDS)?
FDS is a powerful, rules-based set of transaction filters and Internet Protocol (IP) address tools designed specifically to help Web merchants identify, manage and prevent costly fraudulent transactions.

BACK


What processors does Authorize.Net support?
Authorize.Net has a relationship with CardSystems Solutions, Concord EFSnet, First Data Merchant Services (Omaha and Nashville processing platforms), Global Payments, RBS Lynk, Nova Information Systems, Paymentech (Tampa processing platform), and TSYS Acquiring Solutions (SM).

BACK

 

First Name  
Last Name  
Company  
Email  
Phone  
Interested In  
 Home   |   FAQ  |   Rates & Pricing   |   Secure Application   |   About Us   |   Partnerships  |   Contact Us
  Site Map  |   Sites Of Interest
 
NoblePay is an is a registered MSP/ISO of HSBC Bank USA, National Association, Buffalo, NY