Explain It in 30 Seconds
A small business needs to get paid online or through another supported channel.
Its website or staff need a way to submit payment information and receive the result.
Authorize.net supplies that gateway connection and tools around the transaction.
The merchant still needs an acceptance and funding arrangement.
A gateway-only plan and a plan that includes a merchant-account arrangement therefore solve different setup needs. [S38][S39]
The gateway is part of getting paid. It is not the whole business relationship behind a payment.
Where It Sits in Visa
Authorize.net is a separately branded offering within Visa, with its own merchant and reseller relationships.
It supplies collection and transaction-management services rather than operating the card network or requiring every merchant to connect directly to it. [S38]
The Problem It Solved
A smaller merchant needs a processing route, payment result and manageable transaction records, but may lack resources to build that infrastructure.
The gateway makes those functions reusable within the merchant's sales workflow. The developer guidance separates submitting a payment from its later financial stages. [S89]
How It Works — Simple Version
A simplified online payment follows this sequence.
1. The customer provides a supported payment method through the merchant's chosen interface. 2. The merchant's application or hosted form submits the transaction to Authorize.net. 3. The payment is sent through the applicable processing path. 4. The issuer's decision returns to the merchant. 5. The transaction proceeds through the selected capture and settlement workflow. 6. The merchant reconciles the payment with its order and funding records.
The stages serve different purposes.
Authorize.net's technical guidance distinguishes an authorization hold, capture that queues the transaction for settlement and subsequent funding through the acquiring arrangement. [S89]
A successful approval is not the same event as the business receiving its final bank deposit.
Gateway Versus Merchant Account
Gateway
The gateway handles payment information and the connection to processing systems.
It supplies an operating interface for submitting and managing supported transactions.
Merchant-account arrangement
The merchant needs the financial relationship through which accepted payments are funded.
That arrangement can be supplied alongside gateway access or already exist through another provider.
Why the distinction matters
Authorize.net markets gateway-only and broader account-enabled plans. [S39]
A business with an existing arrangement has a different setup problem from one starting without it.
Comparing only the visible gateway charge can miss other acceptance costs.
The full merchant discount also should not be treated as revenue retained by the gateway. Different parties supply different services. [S54]
A Hosted Payment Form Example
Accept Hosted provides an Authorize.net-hosted form that the merchant can redirect to or embed.
The merchant first requests a form token containing transaction information. The customer completes the form, processing follows and the customer returns to the merchant. [S90]
This saves form-building work, while the merchant still connects the result to the order. A hosted component does not certify the security or compliance of the whole business.
Major Payment Workflows
Online payments
A website or application collects an order and submits the relevant payment through its integration.
The customer is buying from the merchant, not signing up for a separate consumer relationship with Authorize.net.
Manual and telephone orders
A virtual terminal lets authorized staff enter supported payments.
That can be useful where the sale occurs outside an automated online cart.
Recurring billing
A business can arrange repeated charges through supported recurring-payment tools.
The payment schedule and the underlying customer authorization are different matters. Technical ability to submit another charge is not permission to charge indefinitely.
Digital invoices
The business sends an invoice and supplies a payment route.
The payment then needs to remain connected to the obligation being collected.
Electronic checks
Electronic-check capabilities provide another supported payment method.
They are not Visa card purchases under a different name and can have different processing and exception requirements. [S38]
These workflows share infrastructure but serve distinct collection needs.
Who Uses It?
Merchants
They use the gateway and operating tools to collect and manage payments.
Their needs depend on how they sell, not merely the size of their website.
Developers and software partners
They connect merchant applications to supported payment functions.
Their implementation affects what the business can offer and how reliably it operates.
Resellers
Authorize.net distributes through independent sales organizations, merchant-service providers and financial institutions.
Those partners can incorporate the gateway into their own merchant proposition. [S38]
Staff and customers
Staff operate transactions and resolve issues.
Customers experience the merchant's payment process, often without selecting the gateway by name.
Why the Reseller Model Matters
A merchant may buy Authorize.net through another organization, affecting setup, billing and support.
The partner reuses gateway infrastructure within its own proposition. The actual agreement—not the gateway logo alone—identifies responsibility for fees, funding and problem resolution.
How the Economics Work
Current plans combine access and transaction-related charges in different configurations. Advertised terms are not a universal quote for every reseller arrangement. [S39]
The merchant compares the complete cost with payment methods, existing acquiring services, software compatibility, billing and support needs.
Purchase principal is not gateway revenue. A low component price can omit another required service; an unused feature can add little value.
What It Depends On
Supported processing arrangements
The gateway needs compatible connections behind the merchant's chosen payment methods.
Capabilities can vary by processor. [S89]
Merchant integration
The website, application or staff workflow must submit the right transaction information and handle the result.
A functioning payment connection cannot repair an incorrect order record.
Access and credential controls
The business needs to control who can submit transactions, issue refunds and operate its systems.
Convenience does not remove those responsibilities.
Customer and transaction records
The merchant must connect a payment to what was sold and delivered.
A gateway cannot manufacture proof of fulfillment or settle every disagreement about the product.
Fraud Tools and Legitimate Payments
Authorize.net supplies rules-based fraud filters and related tools. [S38]
The merchant chooses policies suited to its goods, delivery and customers. Restrictive settings can reject legitimate orders; permissive settings can admit fraud.
The useful result balances losses, valid sales and investigation work rather than maximizing blocks.
What Depends on Authorize.net
Merchants can build online, manual and recurring collections around the gateway; software partners can embed it in wider applications.
Dependence concerns the chosen service and integration. It does not imply a common acquirer, processor or payment mix for every merchant.
Why It Matters to Visa
Authorize.net gives Visa a merchant-level service distributed partly through partners with their own customer relationships.
Its role is practical payment capability for businesses, rather than requiring them to buy a global institutional network connection.
Before / After
Building independently
The merchant must connect its sales interface, processing and payment management.
Using the gateway
It reuses established infrastructure while retaining the goods, customer relationship, order records and operating decisions.
The changed constraint is infrastructure-building work.
What Most People Misunderstand
“A gateway is the merchant's bank account.”
They are different functions, even when sold together.
“Visa ownership means only Visa cards can be accepted.”
“A hosted form proves the whole business is compliant.”
It changes part of the implementation. It does not certify every merchant system or process.
“Recurring billing replaces customer authorization.”
The commercial permission and technical billing schedule remain separate.
“The advertised gateway price is every merchant's total cost.”
Acquiring, partners and selected services can change the combined economics. [S39]
Key Milestones
1996 — Service roots
Authorize.net dates its merchant-payment business to 1996. [S38]
2010 — Visa ownership through Cybersource
Evidence
- [S38] Identity, supported workflows and reseller model.
- [S39] Distinct plan configurations and commercial boundaries.
- [S89] Transaction stages and processor-specific scope.
- [S90] The hosted-form workflow.
- [S54] Distinction between acceptance costs and fees retained by a particular supplier.
- [S17], [S18] Visa ownership and acquisition context.
The merchant comparisons are explanatory analysis, not a recommendation of one plan or a quote for a particular business.