Merchants
1996
in Market
Served
Integrated
Gateway
Authorize.Net, an acquirer-agnostic gateway, an industry-aware payments layer
Authorize.Net (founded 1996) is one of the longest-running payment gateways in the U.S. and is now part of Visa Acceptance Solutions following Visa's acquisition of Cybersource. Its distinguishing feature, compared to processor-owned gateways, is that it's acquirer-agnostic: Authorize.Net connects to virtually every processor and acquiring bank in the U.S., so merchants pick their gateway and their processor independently. With 400,000+ active merchants and the signature CIM / ARB / AFDS stack, it is one of the most broadly deployed gateways in U.S. SMB and mid-market payments. What it does not give you, on its own, is an industry-aware payment experience tuned to the way distributors, manufacturers, healthcare providers, nonprofits, schools, government buyers, professional-services firms, and subscription businesses actually collect money.
That's the layer Clarity Payment Hub supplies. On top of Authorize.Net's gateway, tokenization, recurring, and fraud rails, Payment Hub adds branded industry checkout flows, a self-service customer portal tailored to each vertical, Level 2/3 auto-enrichment for commercial-card programs, eCheck.Net ACH, tokenized recurring billing via ARB, surcharging, and 25+ ERP connectors, so a distributor on Sage, a clinic on Epicor, a nonprofit on NetSuite, and a school on Oracle all get an experience that matches how their industry buys.
What Authorize.Net owns, gateway routing to your acquirer, CIM tokenization, ARB recurring, eCheck.Net, AFDS risk filters, stays with Authorize.Net. What Payment Hub owns, the industry-specific payment pattern, the ERP posting, the customer-facing portal, extends Authorize.Net into the verticals it doesn't reach natively. Your Authorize.Net account, acquiring bank relationship, and negotiated rates all stay exactly as they are.
How Payment Hub connects Authorize.Net to your ERP
Clarity Connect, the integration engine under Payment Hub with 15+ years of active development, reads from and writes to your ERP in real time using each platform's supported API layer, and talks to Authorize.Net via the Authorize.Net API, Accept Hosted, and Accept.js for in-browser tokenization.
Inbound from ERP
Customers, contacts, open invoices with line items, account balances, credits, payment history, statements, all in real time.
Outbound to ERP
Applied cash receipts, CIM payment profile references, address updates, and Pay-on-Account allocations, posted the moment a customer authorizes payment.
Authorize.Net-side processing
Authorize.Net routes to your acquirer, runs AFDS fraud filters, processes through CIM tokenization, and returns the response. Clarity never inserts a spread, skims a basis point, or marks up transaction costs.
No ERP modifications
Clarity Connect uses only documented, supported integration points. No schema changes, no ERP-side custom code, no plugins to maintain across upgrades.
For cloud ERPs (NetSuite, Acumatica, Dynamics 365 BC, SAP S/4HANA Cloud) Clarity Connect talks directly to the ERP's cloud APIs. For on-premise ERPs (Dynamics GP/NAV, Sage 100/300, SAP ECC, Oracle EBS, SYSPRO, Epicor P21/Eclipse/Eagle) we use a lightweight outbound-only secure agent that calls from inside your network, no inbound firewall ports to open.
Industries Authorize.Net + Payment Hub serves
Authorize.Net is the most broadly deployed gateway in U.S. SMB and mid-market, with 400,000+ merchants spanning every vertical. On its own, it's platform-shaped, not industry-shaped. Paired with Clarity Payment Hub, Authorize.Net becomes an industry-aware payments platform across the eight verticals Clarity has supported for 20+ years.
B2B Distribution &, Wholesale
Commercial-card-heavy AR, line-item invoices, customer-specific pricing, and Level 2/3 interchange savings on every eligible card.
- Level 2/3 auto-enrichment from ERP line-item data
- Customer portal with open invoices, short pays, credits
- eCheck.Net + card side-by-side on the same invoice
- CIM one-click re-pay for repeat B2B buyers
Manufacturing
Progress billing, milestone invoicing, deposits on long build cycles, and commercial-card programs from industrial buyers.
- Deposits and milestone payments tied to sales orders
- ARB recurring for service and maintenance contracts
- Level 2/3 on dealer and distributor commercial cards
- Real-time posting so production doesn't wait on AR
Healthcare &, Life Sciences
Patient pay, payment plans, HSA/FSA card acceptance, and practice-management posting without PHI leaking into payment flows.
- Branded patient portal with balance and plan visibility
- ARB recurring for payment plans
- HSA/FSA and commercial card acceptance
- Posting to the practice-management or ERP system
Nonprofit &, Fundraising
Donation pages, recurring giving, pledges, tributes, and event registration, all posting to the fund-accounting GL.
- Branded donation and giving pages
- ARB recurring donations with CIM tokenization
- Designation and campaign tracking to the GL
- eCheck.Net for larger recurring gifts at lower cost
Education
Tuition, fees, lunch accounts, enrollment, and continuing-ed registration, consolidated under one payment layer.
- Tuition payment plans with ARB recurring
- Branded parent / student portal with CIM wallet
- eCheck.Net for larger tuition payments to reduce fees
- Posting to SIS / ERP for real-time balance updates
Government &, Public Sector
Permit, license, utility, and citation payments with CEDP-ready Level 3 and clean audit trails back to the financial system.
- CEDP-ready Level 3 on every commercial-card transaction
- Branded citizen payment portals
- Fee-pass-through and convenience-fee configurations
- Posting to Tyler, Oracle, SAP, or Dynamics financials
Professional Services &, Agencies
Retainers, project billing, trust/IOLTA segregation, and hourly invoices, paid the same day they're sent.
- Pay-by-link and branded invoice payment pages
- Trust / IOLTA account segregation for legal workflows
- ARB recurring for retainers and monthly services
- Real-time posting to the PSA / ERP
Subscription, SaaS &, Membership
Recurring billing, dunning, proration, and card-updater, posted in real time to the subscription or ERP system of record. ARB has been the backbone of subscription billing on Authorize.Net since the late 90s.
- ARB subscriptions with CIM tokenized recurring
- Dunning, retry, and failed-payment recovery flows
- Branded member / subscriber portal
- Real-time posting to the billing / ERP system
We can typically go live in 48 hours once ERP sandbox credentials and Authorize.Net API login / transaction key are shared. Skip the reading and book a 30-minute walkthrough of your industry's exact flow.
The Missing LinkBetween Paymentsand Your ERP
Clarity Payment Hub closes that gap, connecting your orders, invoices, and payment channels into one flow.
Speak to a Platform ArchitectEvery payment method your customers need
Authorize.Net supports the full stack of U.S. payment methods. Payment Hub surfaces the ones that matter per industry, and lets you hide the ones that do not.
Cards
Visa, Mastercard, American Express, Discover, JCB, Diners, including commercial, corporate, and purchasing cards that qualify for Level 2/3 rates through your acquirer.
eCheck.Net (ACH)
Authorize.Net's native ACH service, U.S. bank-account transfers at the lowest per-transaction cost available for large B2B tickets. Tokenized in CIM once, re-used in one click forever.
Digital Wallets
Apple Pay, Google Pay, and PayPal surface inside the Authorize.Net-powered Payment Hub checkout. Wallet transactions flow through Authorize.Net to your acquirer like any tokenized card transaction.
Visa Checkout / Click to Pay
Visa's interoperable guest-checkout standard (EMV SRC) renders alongside Authorize.Net card entry in the checkout, reducing card-entry friction for repeat Visa buyers.
For large B2B accounts, we commonly set eCheck.Net as the default payment method above a configurable dollar threshold, protecting your card-processing economics on seven-figure invoices while still giving customers a one-click experience via CIM.
Interchange savings and compliant surcharging
Two of the biggest unit-economics levers in B2B payments, Level 2/3 enhanced data and credit-card surcharging, ship in Payment Hub out of the box on top of Authorize.Net.
Level 2 and Level 3 processing
Level 2 and Level 3 refer to enhanced transaction data (sales tax, customer code, invoice line items, purchase order number, freight, duty, product codes) that the card networks require to qualify large B2B transactions for the lowest interchange tiers. Without this data, B2B card transactions default to the most expensive commercial-card interchange.
Authorize.Net supports Level 2/3 data passing on qualified Visa and Mastercard commercial cards, plus CEDP (Customer-Defined Enhanced Data Program) for U.S. federal and state government purchasing. Clarity Payment Hub pulls the line-item, tax, and customer-code data from your ERP automatically and passes it to Authorize.Net on every eligible transaction. There is nothing for your AR team to key in and nothing for the customer to fill out.
Compliant credit card surcharging
Payment Hub supports compliant credit card surcharging out of the box on Authorize.Net. The platform handles state-by-state rule enforcement, displays the legally required pre-authorization disclosure, caps the surcharge percentage at the allowed maximum (typically 3% per card network rules), and tracks the surcharge as a separate line in your ERP. Debit cards, prepaid cards, and non-surcharge-eligible cards are excluded automatically.
Cash-discount programs, where the invoice price already includes processing and non-card methods get a discount, are also supported. Your choice between the two models depends on your state, your customers' expectations, and your pricing strategy.
CIM, ARB, and AFDS, the signature Authorize.Net stack
Three Authorize.Net capabilities have been the backbone of U.S. merchant payments since the late 1990s, Customer Information Manager, Automated Recurring Billing, and the Advanced Fraud Detection Suite. Payment Hub wires each of them into the industry-aware flow.
CIM, Customer Information Manager
Authorize.Net's PCI-scoped tokenization vault. Replaces PAN and bank-account data with tokens, stores payment profiles and shipping profiles per customer. Payment Hub uses CIM as the system of record for every saved method, so one-click re-payment is the default experience and PAN never touches your infrastructure.
ARB, Automated Recurring Billing
Weekly, monthly, quarterly, annual, trial period, fixed or unlimited occurrences. Payment Hub drives tuition payment plans, healthcare payment plans, donation recurring giving, membership dues, SaaS subscriptions, and retainer billing through ARB, with retry, dunning, and card-updater logic layered on top.
AFDS, Advanced Fraud Detection Suite
13+ configurable risk filters, IP velocity, card velocity, amount thresholds, shipping/billing mismatch, high-risk countries, shipping-to-billing zip comparison, hourly limits. Payment Hub exposes AFDS decisioning inside the AR workflow so suspicious orders surface for review before settlement.
Accept Hosted &, Accept.js
Two implementation modes. Accept Hosted redirects to an Authorize.Net-hosted page for SAQ A scope. Accept.js tokenizes in-browser and never exposes PAN to your servers, also qualifying for SAQ A. Payment Hub supports both depending on your brand and PCI preference.
Together these four capabilities mean Authorize.Net handles the hard parts, tokenization, recurring orchestration, fraud scoring, PCI-minimized card entry, while Payment Hub handles the industry context, which customer, which invoice, which vertical, which ERP. Neither side duplicates the other's work.
Security, PCI scope, and Visa-backed compliance
Authorize.Net is PCI DSS Level 1 certified, the highest tier, and operates under Visa Acceptance Solutions, with Visa's compliance and security infrastructure behind it. Clarity Payment Hub is built to push your deployment to the lightest compliance scope available.
- Tokenization at Authorize.Net CIM. Every card and ACH account is tokenized directly at Authorize.Net's PCI-certified Customer Information Manager vault. Raw card numbers never touch Payment Hub's infrastructure and never touch your servers.
- Accept.js + Accept Hosted. Card data is captured and tokenized either in the customer's browser (Accept.js) or on an Authorize.Net-hosted page (Accept Hosted), so PAN never transits Payment Hub or your servers. Either mode qualifies for SAQ A, the lightest PCI self-assessment available.
- SOC 2 Type II. Clarity Ventures operates to SOC 2 Type II standards. Security, availability, confidentiality, and data-handling controls are independently audited on an ongoing basis.
- AFDS + 3D Secure. Authorize.Net's AFDS risk filters, AVS, CVV, velocity checks, and 3D Secure 2 step-up authentication combine with portal-level controls (invoice-bound authentication, customer-matched billing addresses, single-use signed Quick Pay links) for a defense profile tuned to B2B invoice fraud, not consumer card fraud.
- Outbound-only agent for on-premise ERPs. No inbound firewall ports. No VPN tunnel. No public ERP exposure.
Authorize.Net + Payment Hub FAQ
The questions B2B AR, IT, and finance teams ask before rolling out Authorize.Net through Clarity Payment Hub.
Which industries does Authorize.Net + Clarity Payment Hub serve?
Eight verticals out of the box: B2B distribution and wholesale, manufacturing, healthcare and life sciences, nonprofit and fundraising, education, government and public sector, professional services and agencies, and subscription / SaaS / membership.
Each vertical gets an industry-aware payment pattern on top of Authorize.Net's gateway, branded portals, real-time ERP posting, Level 2/3 data enrichment, eCheck.Net ACH, CIM-tokenized recurring via ARB, AFDS fraud scoring. The same 48-hour rollout and 25+ ERP connector library covers every vertical, so a distributor on Sage, a clinic on Epicor, a nonprofit on NetSuite, and a municipality on Oracle all get an experience that matches how their industry buys.
Does Authorize.Net support ACH and eCheck transactions?
Yes, eCheck.Net is Authorize.Net's native ACH processing service, fully integrated with the same API and merchant interface as card processing. Clarity Payment Hub exposes ACH as a first-class payment method in the portal and the tokenized wallet, which is typically the lowest-cost method for high-dollar B2B invoices.
Bank details are tokenized in CIM so customers re-use them in one click without re-entering routing and account numbers. Many customers set eCheck.Net as the default on invoices over a defined dollar threshold to protect card-processing economics on large tickets.
What is Authorize.Net CIM and how does Payment Hub use it?
Customer Information Manager (CIM) is Authorize.Net's PCI-scoped tokenization vault. It replaces raw card numbers and bank accounts with tokens and stores payment profiles and shipping profiles per customer. CIM has been the backbone of Authorize.Net merchant tokenization for nearly two decades.
Clarity Payment Hub uses CIM as the system of record for every saved card and ACH account, then references the token in the ERP. Raw PAN never touches Payment Hub or your infrastructure, and one-click re-payment from the customer portal is the default experience. For long-running B2B relationships, this means repeat buyers never have to re-enter payment details.
Can Authorize.Net pass Level 2 and Level 3 data for interchange savings?
Yes. Authorize.Net supports Level 2 and Level 3 enhanced data on qualified Visa and Mastercard commercial-card transactions, plus CEDP (Customer-Defined Enhanced Data Program) for U.S. government purchasing. Clarity Payment Hub pulls the line-item, tax, and customer-code data from your ERP automatically and passes it to Authorize.Net on every eligible transaction.
B2B merchants commonly save 0.5–1.0% (up to 30% off transaction fees) of each eligible card transaction when Level 2/3 data is passed correctly. On a $50,000 invoice that is $250–$500 of margin preserved, on every transaction.
What is ARB and how does it handle recurring billing?
Automated Recurring Billing (ARB) is Authorize.Net's scheduled-payment engine, weekly, monthly, quarterly, annual, trial periods, fixed or unlimited occurrences. Clarity Payment Hub uses ARB to drive tuition payment plans, healthcare payment plans, recurring donations, membership dues, SaaS subscriptions, and retainer billing, all with tokenized credentials living in CIM.
Failed-charge retry, card-updater, and dunning logic are wired through Payment Hub so recovery happens without manual AR intervention. Every recurring charge posts to the right customer, the right invoice, and the right GL account in real time through the ERP integration.
How does Clarity Payment Hub handle Authorize.Net settlements?
Authorize.Net routes the transaction to your acquiring bank. Your acquirer settles and funds on its own schedule. What Clarity Payment Hub changes is the ERP side: the applied cash receipt is written back to your ERP in real time the moment the customer pays, before the bank funds settle.
There is no overnight batch, no CSV import, and no manual cash application. Invoice status, account balance, and aging reports update immediately in your ERP, which is how the DSO drop and the AR-time savings become real.
What is the integration cost and timeline for Authorize.Net through Payment Hub?
Clarity Payment Hub is packaged software, not a custom build. A typical Authorize.Net + ERP go-live takes 48 hours once Clarity receives ERP sandbox credentials and Authorize.Net API login ID and transaction key. No new servers, no middleware, no custom code on your ERP.
You keep your Authorize.Net account, your acquiring bank relationship, and your negotiated rates, Clarity does not insert a transaction markup or skim basis points. Implementation is a flat subscription with the ERP integration included.
Is Authorize.Net PCI compliant and how does it affect our own PCI scope?
Authorize.Net is PCI DSS Level 1 certified, the highest tier, and is owned by Visa via the Cybersource acquisition, under the Visa Acceptance Solutions umbrella. Clarity Payment Hub uses Accept.js and Accept Hosted to tokenize card data directly in the customer's browser or on Authorize.Net-hosted pages, meaning raw PAN never reaches your servers, Payment Hub's servers, or the network in between.
Most deployments qualify for SAQ A, the lightest PCI self-assessment available. That means a dramatically shorter annual compliance review, no cardholder-data environment to audit, and significantly lower risk of breach exposure.
Does Authorize.Net support surcharging?
Yes. Payment Hub supports compliant credit card surcharging on Authorize.Net card transactions, state-by-state rules, network caps, and the legally required pre-authorization disclosure are all enforced automatically. Debit, prepaid, and non-eligible cards are excluded from surcharging.
Cash-discount programs are also supported where your pricing strategy calls for it. Surcharging and cash discounting are configurable per vertical, per customer segment, and per invoice dollar threshold.
How does Authorize.Net + Payment Hub compare to an ERP-native payment module?
ERP-native payment modules typically force you onto one processor at rates you cannot negotiate, and rarely provide a true customer-facing portal, CIM-style tokenization, or ARB-style recurring at the level Authorize.Net delivers. Authorize.Net + Payment Hub keeps you on Authorize.Net's gateway (with your existing acquirer), adds a branded self-service buyer experience, passes Level 2/3 data automatically to unlock the lowest B2B interchange tiers, and gives your AR team real-time cash application.
ERP-native modules solve for the ERP. Authorize.Net + Payment Hub solves for the customer experience and your unit economics, which is where AR modernization actually pays back.
Can we move to Authorize.Net if we are currently on another gateway?
Yes, and Clarity Payment Hub is designed to make that transition painless. Because Payment Hub is gateway-agnostic, you can port your portal, your ERP integration, your customer accounts, and your buyer UX from your current gateway to Authorize.Net without rebuilding any of them. The only piece that changes is the gateway credential. Tokenized cards are re-vaulted into CIM during migration, and ARB subscriptions are recreated with the original billing schedule preserved.
Because Authorize.Net is acquirer-agnostic, you also don't need to change your acquiring bank if your current relationship is working, Authorize.Net connects to virtually every U.S. acquirer.