Gateway Options When Authorize.net Turns You Down
A gateway does not underwrite anyone. An acquiring bank declined you, and under US Visa rules it cannot lock you to its own gateway either.
By Jeffrey Anderson
- Authorize.net is a gateway. The decline came from an acquiring bank underwriting the merchant account bundled with it, not from the gateway software.
- Visa Core Rules Section 5.2.1.2 (ID# 0005251) requires an Acquirer or Payment Facilitator to conduct an adequate due diligence review, including a site visit or suitable alternative, before contracting with a prospective merchant.
- Section 5.2.1.5 (ID# 0003362) applies in the US Region and bars an Acquirer from prohibiting a merchant from using a competitor's terminal processing services, so gateway and merchant account are separable.
- A bank is not obliged to tell you why it declined you. That is commercial discretion, not a network rule.
- Moving to a second aggregator repeats the risk rather than solving it. A dedicated MID is underwritten directly and the gateway becomes a choice.
Authorize.net is a gateway. A gateway does not underwrite anyone. If you got a decline, what turned you down was an acquiring bank's review of your business, not the software you applied through. That distinction matters, because it changes what you do next. Shopping for a different gateway will not fix an underwriting problem, and reapplying to the same bank through a different front door usually lands in the same place.
Here is what actually happened, and what your options are.
What a gateway does and does not decide
The gateway encrypts the card data, sends the authorization request, and hands back the response. That is the whole job. We broke the cost of that job down in gateway fees for high risk merchants.
What it does not do is decide whether your business gets a merchant account. That decision sits with an acquirer. When a gateway is sold as an all-in-one package, a merchant account comes bundled with it, and the decline you received came from the bank behind the bundle. The gateway brand on the email is just the brand you applied through.
The rule that says a bank has to look at you first
Section 5.2.1.2 of the Visa Core Rules (ID# 0005251) is short and worth reading in full:
Before contracting with a prospective Merchant or Sponsored Merchant, an Acquirer or a Payment Facilitator must conduct an adequate due diligence review, including a site visit to the business premises (if applicable) or suitable alternative, to ensure compliance with the Acquirer's obligation to submit only legal Transactions to VisaNet.
Two things follow from that. The bank is required to review you, so a decline is a review result rather than a software error. And the standard it is reviewing against is whether it can submit only legal transactions, which is why your industry, your website and your refund policy matter more than your credit score.
A bank that declines you is not obliged to tell you why. That is a commercial decision, not a rule.
Your acquirer cannot lock you to its gateway
This is the part almost nobody tells merchants, and it is the reason you have more options than the decline email suggests.
Section 5.2.1.5 (ID# 0003362) applies in the US Region:
An Acquirer must not prohibit a Merchant from using terminal processing services offered by competitors for the direct delivery of Visa Transactions captured at the Point-of-Transaction to VisaNet for Clearing and Settlement.
Your acquirer cannot contractually forbid you from using a competitor's processing services at the point of sale. Gateway choice and merchant account are separable. If a provider tells you that taking their account means taking their gateway and nothing else, that is their commercial preference, not a network requirement.
What your options actually are
Three routes, in the order most merchants should try them.
Get a dedicated merchant account and keep the gateway separate. This is the normal structure for anything the mainstream bundles will not take. You are underwritten directly, you get your own MID, and the gateway becomes a choice rather than a package deal. Our payment gateways page lists what each platform supports.
Understand why the bundle said no before you reapply. Most all-in-one declines are category decisions made by the aggregator, not judgments about your specific business. What actually makes a business high risk walks through the categories.
Do not simply move to another aggregator. A second pooled account has the same freeze risk as the first, which we cover in dedicated vs pooled merchant accounts. Being accepted quickly is not the same as being underwritten.
What to have ready before you reapply
The due diligence review is the gate, so give it what it needs the first time. A working website with your refund and cancellation policy visible. A description of what you actually sell, in plain words. Processing history if you have any. Bank statements. An explanation of any prior account closure, written by you rather than discovered by them.
Volunteering the awkward part is usually better than letting a bank find it. A merchant who explains a past chargeback spike reads as someone who understands their own risk. A merchant who omits it reads as someone who hid it.
Frequently Asked Questions
Will a bank tell me why it declined me?
Usually not, and it is not required to. What you can do is ask your next provider what in your profile is likely to be the sticking point, then address that directly in the application rather than guessing.
Jeffrey Anderson, Merchant Placement Specialist
Merchant placement specialist at Gray Merchants. Jeffrey works directly with acquiring-bank underwriting teams across the firm’s 70+ banking relationships to place high-risk and hard-to-place businesses, structure multi-MID accounts, and keep flagged merchants processing. His writing draws on the placement files he works every week: what underwriters ask for, why accounts get declined, and what keeps an approved account open.