Con · Retail · Prof Svc
Supported
Use Cases
API Integration
Timeline
Why Acumatica customers add Payment Hub, and what changes when they do
Compared to all other Enterprise ERPs, Acumatica is relatively new to the ERP space. Acumatica is one of the fastest-growing cloud ERPs in the mid-market, 10,000+ customers, six industry editions, a modern Cloud xRP platform built on standard web technologies with open APIs. It handles financials, AR, AP, sales orders, inventory, projects, and CRM cleanly, and recent releases (including 2026 R1) have added AI Studio, AI Assistant, and stronger supply-chain tooling. Payment Hub extends Acumatica on the payment-acceptance side, the one area where the native options don't go far enough for most B2B, multi-location, and mid-market operations.
So can Payment Hub really help with Acumatica payment processing? The answer is absolutely. The reality of payment acceptance on Acumatica today: the native Acumatica Payments layer handles invoice payments and pay-link emails cleanly against a single built-in processor. It does what it does well, but it leaves four gaps that most Acumatica customers feel, especially in Distribution, Manufacturing, Construction, and Retail editions:
- Gateway lock-in. Acumatica Payments is a single processor. If you've negotiated pricing with Worldpay, Fortis, PayTrace, PNC, or any other gateway, or if your industry requires a specific acquirer for Level III pricing, the native path doesn't fit.
- Invoice-only, not order-entry payment. Native payment is centered on the AR invoice. Order-entry payments (sales-rep phone orders, deposits on configured-to-order manufacturing, field-service job completion) aren't natively handled.
- No Level III automation. Commercial-card B2B customers on Acumatica routinely pay L1 interchange when they could be paying L3, because the 20+ required fields aren't auto-enriched from the Acumatica invoice at submission.
- Limited customer-portal self-service. Pay-links work for a single invoice or sales order. A full customer self-service portal (balance, aging, credits, saved methods, autopay, multi-invoice consolidation, subscription management) is a separate build.
All six Acumatica editions, where Payment Hub fits in each
Acumatica ships in six editions, each with a shared core (Financials, AR, AP, Sales Order, Inventory, Projects, CRM) plus edition-specific extensions for its target industry. Payment Hub integrates with all six, and the payment-acceptance patterns that matter most differ per edition.
General Business Edition
The baseline edition, financials, CRM, project accounting, reporting. Common for service businesses, nonprofits, and mid-market orgs whose operations don't fit a specific vertical template.
Distribution Edition
Wholesale distribution, warehouse management, advanced inventory, purchase order, requisition, and sales-order workflows. Strong for regional distributors, industrial supply, and B2B wholesalers.
Manufacturing Edition
Production planning, MRP, BOM, shop floor, engineering change. Suited for make-to-order, configure-to-order, and discrete manufacturers with Acumatica's native manufacturing modules layered on Distribution.
Construction Edition
Project accounting, progress billing, retention, compliance management, sub-contractor tracking. Purpose-built for general contractors, specialty subs, home builders, and construction service firms.
Retail Edition
Omni-channel commerce, connects in-store, eCommerce, and back-office inventory. Native integrations with Shopify, BigCommerce, Magento plus Acumatica's own commerce layer.
Professional Services Edition
Project accounting, time and expense, resource management. Built for consulting firms, engineering firms, legal, accounting, and professional services where time-and-materials and fixed-fee project billing dominate.
Regardless of edition, the integration works through the same Acumatica Web Services API layer, so the engineering effort doesn't vary by edition. What changes is which Payment Hub use cases are most relevant and which industry-specific Acumatica fields flow into payment enrichment (project codes for Construction / Professional Services. Item master and warehouse routing for Distribution / Manufacturing. Commerce-order context for Retail).
Payment Hub vs native Acumatica Payments, what you get with each
Native Acumatica Payments is a capable invoice-payment layer for customers who want the simplest built-in path. Payment Hub is the gateway-agnostic alternative for customers who need more, more gateway options, more payment patterns, more automation, and more visibility. Here's the honest side-by-side.
| Capability | Native Acumatica Payments | Payment Hub on Acumatica |
|---|---|---|
| Gateway / processor choice | ✗ Single native processor, Authorize.Net discontinued after 2023 R2 | ✓ 19+ gateways (Worldpay, Adyen, Cybersource, Fortis, PayTrace, Stripe, Braintree, PNC, Elavon, Global Payments, NMI, USAePay, Square, wallets, ACH) |
| Invoice payment (AR-generated) | ✓ Pay-links &, QR codes on invoices | ✓ Plus branded customer portal, multi-invoice consolidation, partial-pay, credit application |
| Order-entry payment (sales order) | ~ Pay-link on sales order | ✓ Embedded in sales-order screen for reps. Deposit, auth-only, capture-at-ship, partial-shipment captures |
| Level III interchange optimization | ✗ Not auto-enriched, B2B merchants typically downgrade to L1 | ✓ Automatic 20+ field enrichment from Acumatica invoice. 0.3–1.0% Savings per qualifying transaction |
| Customer self-service portal | ~ Per-invoice pay-link | ✓ Full portal, balance, aging, credits, saved methods, autopay, history, statements, with matching team-facing view |
| Subscription billing (recurring / scheduled / automated) | ~ Recurring via Acumatica's native recurring-invoice modules | ✓ Native recurring + scheduled installments + event-triggered auto-pay. Dunning, Account Updater, proration |
| Multi-branch / multi-company routing | ~ Inherits Acumatica's branch structure, limited MID-per-branch options | ✓ Per-branch MID, tax, GL, and staff role mapping over Acumatica's branch / company structure |
| Counter / card-present acceptance | ✗ Not a POS-first design | ✓ 150+ certified terminals, Tap to Pay iPhone / Android, ERP-customer lookup at counter |
| AR collections automation (dunning) | ~ Basic overdue notifications | ✓ Full dunning engine with configurable cadence, pay-links in emails, DSO reduction tracking |
| Keep existing merchant account / processor | ✗ Requires migration to Acumatica Payments | ✓ Your existing gateway, merchant account, and negotiated rates carry forward |
The verdict: native Acumatica Payments is the simplest option if you're starting from scratch, have modest volume, don't need B2B L3 optimization, and are comfortable with a single-processor path. Payment Hub is the right fit the moment any of those assumptions break, which is most B2B, multi-location, and mid-market operations on Acumatica.
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 ArchitectHow Clarity Connect integrates Payment Hub with Acumatica
The integration is built on Acumatica's standard Web Services API layer. No custom ERP extensions, no schema changes, no unsupported modifications. Every payment event, authorization, capture, refund, credit application, posts through documented API endpoints to the correct Acumatica record in real time.
Customer &, invoice lookup
Payment Hub reads Acumatica's Customer, Invoice, and Sales Order records in real time for balance lookup, payment matching, and line-item L3 enrichment. Uses standard API endpoints, no custom entity extensions required.
Real-time cash receipt posting
Every capture posts as an Acumatica Payment and Application record at the moment the gateway authorizes, applied to the correct AR invoice with the right payment method, amount, reference, and audit detail. No end-of-day batch.
Tokenized method vault
Customer card and ACH credentials tokenize at the gateway's PCI-scoped vault, never stored on Payment Hub or Acumatica servers. Tokens link to the Acumatica Customer record via custom fields for repeat-use across portal, counter, field, and sales-rep channels.
Level III auto-enrichment
On commercial-card transactions, Payment Hub pulls line items, UoM, product codes, tax, freight, and customer code from the underlying Acumatica invoice and packages the full L3 envelope for the gateway, no manual field mapping, no per-transaction data entry.
Multi-branch / multi-company aware
Acumatica's native Branch and Company constructs map into Payment Hub's location routing table. Payment at Acumatica Branch DLX-01 posts to that branch's Cash GL and warehouse. Payment at OAK-02 routes to OAK-02, with the correct MID, tax, and GL per branch automatically.
Subscription scheduler + dunning
Native recurring, scheduled, and automated billing runs against Acumatica's recurring-invoice records (or Payment Hub's own schedule engine). Dunning logic retries soft declines. Account Updater refreshes reissued cards silently. Customer portal handles self-enrollment.
Branch-aware audit &, reporting
Every transaction logs which Acumatica branch / company / user initiated it, which gateway it routed through, which L3 tier it qualified for, and what the resulting Acumatica journal entry looked like. Head-office consolidated dashboard across branches.
No Acumatica-side code to maintain
The integration lives in Clarity Connect, which reads and writes through Acumatica's standard Web Services API. No custom Acumatica Customizations, no schema modifications, no unsupported code paths, so Acumatica version upgrades (including 2026 R1 and future releases) don't break the integration.
The integration workflow, from Acumatica invoice to posted cash
A concrete walk-through: an Acumatica Distribution Edition customer receives a $4,820 invoice, pays it from the customer portal with a Visa Purchasing card, and watches the cash application land in Acumatica in real time, all within 90 seconds, with L3 interchange savings captured automatically.
Acumatica generates the invoice
Your AR team (or automated workflow) creates invoice INV-48210 in Acumatica for Acme Manufacturing, $4,820 covering 10 line items, Dallas branch origin, Texas tax jurisdiction, Net 30 terms. Invoice saves to Acumatica and becomes visible through the standard Acumatica Invoice API endpoint.
Acumatica AR Standard APICustomer sees it in the Payment Hub portal
Acme's AP manager logs into your branded Payment Hub portal (pay.yourcompany.com). Clarity Connect fetches Acme's live Acumatica data, $4,820 new invoice visible, total outstanding $18,240 across three invoices, $320 available credit from last month, Visa saved on file from prior payment.
Live Acumatica fetch Branded portalCustomer selects &, pays
AP manager selects INV-48210 to pay in full with their saved Visa Purchasing card (BIN identified as commercial-eligible). Payment Hub recognizes the commercial BIN and flags the transaction for L3 enrichment before submission.
Saved method BIN checkClarity Connect pulls L3 data from Acumatica
Payment Hub queries Acumatica's Invoice + Sales Order APIs to fetch line items (10 × widgets), UoM mappings, product codes, tax breakdown ($380 state + county), freight ($42), customer code (ACME-4021), and destination ZIP. All 20+ L3 fields packaged into the gateway envelope in under 250ms.
20+ L3 fields 250ms fetchGateway authorizes at L3 interchange
Whichever gateway you run (Worldpay, Fortis, PayTrace, Stripe, whatever was configured) receives the full L3 envelope. Visa qualifies the transaction at the Level III interchange category, roughly 1.05% savings vs. L1 on this $4,820 transaction = $50 of direct interchange savings.
Your gateway ~$50 savedClarity Connect posts back to Acumatica
Payment Hub writes a Payment record to Acumatica ($4,820, Visa ending 4421, Dallas branch, Texas GL 1010-DLX) and applies it against INV-48210 through the standard Payment Application API. Invoice closes to $0 balance. Clarity Connect responds to Payment Hub with the Acumatica-generated payment reference number.
Real-time post Invoice closedCustomer sees success, your team sees activity
Portal shows "Payment successful, $4,820 applied." Receipt email sent. Your AR team's Payment Hub dashboard picks up the transaction in real time, rep sees Acme's balance drop to $13,420, invoice closed, L3 savings of $50 logged. Total elapsed time: 90 seconds from login to posted cash in Acumatica.
90s end-to-end Zero staff timeMonth-end reconciliation is a check, not a project
At month-end, your controller runs the standard Acumatica AR aging report and cash GL reconciliation. Every Payment Hub transaction for the month is already posted. Every invoice closed has an attached payment record. Every GL entry reconciles. Because the integration is real-time all month long, month-end takes hours, not weeks.
Month-end in hoursPayment Hub use cases on Acumatica
Every Payment Hub use case runs on top of the Acumatica integration. The patterns most common by edition are highlighted, but all 11 are available, configurable based on which workflows your business actually uses.
Pay-link emails, portal, L3-enriched commercial-card acceptance for every Acumatica-generated invoice.
Order-entry Order-to-CashPayment embedded in Acumatica's sales-order screen, deposits, auth-only, capture-at-ship, partial captures.
Customer-facing Self-Service Payment PortalBranded portal reading live Acumatica data, customers pay, your team sees the same picture.
Recurring Subscription BillingNative recurring, scheduled, and automated billing, runs alongside Acumatica's recurring-invoice features.
Cost reduction Level III InterchangeAuto-enrich qualifying commercial-card transactions from Acumatica invoice data. 0.3–1.0% savings.
Card-present Counter Sales &, RetailFor Distribution / Retail editions running parts counters, will-call, and retail storefronts.
Multi-branch Multi-Location PaymentsPer-branch MID, tax, and GL routing over Acumatica's native branch / company structure.
Back-office ERP Payment ReconciliationReal-time cash application, end the CSV-to-Acumatica-import era for good.
Aging reduction AR Collections AutomationDunning cadences with direct pay-links, DSO reduction of 5–12 days typical.
Batched pay Consolidated Invoice PaymentCustomers pay multiple Acumatica invoices in one transaction. Payment Hub splits clean per-invoice.
Online orders eCommerce CheckoutRetail Edition's commerce connector pairs with Payment Hub for unified storefront checkout.
Technical details, what's actually happening under the hood
The engineering reality of how Clarity Connect integrates Payment Hub with Acumatica, for IT teams, controllers, and anyone who wants to know more than the marketing layer before committing.
- API layer. Integration uses Acumatica's standard Web Services APIs (Contract-based REST/SOAP endpoints for Customer, Invoice, Sales Order, Payment, Payment Application, and Cash Transaction entities). No ODATA-only dependency, no custom entity extensions required for the baseline integration.
- Authentication. OAuth 2.0 against Acumatica's authentication endpoint. Tokens refresh automatically, secrets held in Payment Hub's encrypted configuration, never exposed to Acumatica users.
- Deployment model. Works with Acumatica SaaS (hosted by Acumatica), private cloud (hosted by your cloud partner), and on-premise deployments. For on-prem, Payment Hub uses the same API endpoints reached through your firewall rules (outbound-only from the Acumatica server in most deployment patterns).
- Version compatibility. Supported on Acumatica 2023 R1, 2023 R2, 2024 R1, 2024 R2, 2025 R1, 2025 R2, and 2026 R1. Compatibility layer handles API schema differences between versions transparently.
- Acumatica customizations. Works alongside custom Acumatica Customization Projects, workflow automations, generic inquiries, and ISV apps. The integration only reads/writes the standard entities. Your existing customizations stay untouched.
- Multi-entity / multi-branch support. Native support for Acumatica's Branch and Company constructs. Acumatica Intercompany Accounting relationships are honored when cash receipts cross entity boundaries.
- PCI scope. Raw PAN never touches Payment Hub or Acumatica servers, card data tokenizes at the gateway vault via hosted iframe / JS-tokenization. Typical deployment stays in SAQ A / SAQ A-EP scope.
- SOC 2 Type II. Clarity Ventures operates to SOC 2 Type II standards with independent annual audits covering security, availability, confidentiality, and data handling.
- Monitoring &, observability. Full audit log in Payment Hub of every Acumatica API call, every transaction, every retry. Integration health dashboard surfaces API latency, error rates, and posting success in real time.
- Rate limits. Respects Acumatica's API rate limits with automatic backoff on throttle responses. For high-volume merchants (100+ transactions / minute at peak), Clarity tunes request pacing to stay well within tenant limits.
Acumatica + Payment Hub FAQ
The questions operations, IT, finance, and Acumatica admins ask before adding Payment Hub to their Acumatica deployment.
Does Clarity Payment Hub integrate with Acumatica?
Yes. Clarity Payment Hub integrates directly with Acumatica Cloud ERP through Clarity Connect, writing to Acumatica's standard Web Services APIs. Every transaction, invoice payment, order payment, deposit, authorization, capture, refund, credit application, posts to Acumatica in real time. Customer records, invoice records, sales order records, and cash receipt records stay as the single source of truth in your Acumatica tenant.
The integration works with all six Acumatica editions (General Business, Distribution, Manufacturing, Construction, Retail, Professional Services) and supports multi-branch / multi-company / multi-warehouse posting patterns.
How is this different from Acumatica's native Acumatica Payments?
Acumatica Payments is a single native processor baked into the Acumatica platform. Clarity Payment Hub is gateway- and processor-agnostic, it integrates Acumatica with any of 19+ supported gateways (Worldpay, Adyen, Cybersource, Global Payments, Elavon, Fortis, PayTrace, Nuvei, PNC Merchant Services, Stripe, Braintree, Authorize.Net, NMI, USAePay, Square, PayPal, Apple Pay, Google Pay, Amazon Pay) plus ACH / eCheck.
You keep your existing merchant account, your existing processor, and your negotiated interchange rates. Payment Hub also extends the integration beyond invoice-payment to order-entry payment, deposit capture, subscription billing, and customer self-service portal, capabilities that go beyond what the native Acumatica Payments layer handles.
What Acumatica editions does Payment Hub support?
All six, General Business Edition, Distribution Edition, Manufacturing Edition, Construction Edition, Retail Edition, and Professional Services Edition. The integration uses Acumatica's standard Financials / AR / Sales Order / Inventory modules that underpin every edition, plus edition-specific extensions where relevant (project billing for Construction and Professional Services, warehouse and item-master awareness for Distribution and Manufacturing, eCommerce-order handling for Retail).
Payment Hub's multi-branch / multi-company routing maps directly onto Acumatica's native multi-branch and multi-company organizational structures.
Does it work with the new Acumatica 2026 R1 release?
Yes. Payment Hub's integration is built on Acumatica's stable Web Services API layer, which is maintained across releases. The integration is compatible with Acumatica 2026 R1 (released March 2026), 2025 R2, 2025 R1, and all recent supported versions.
New Acumatica capabilities that affect the invoice / AR / sales-order data model, including 2026 R1's AI Studio, AI Assistant, and supply-chain enhancements, work alongside Payment Hub without requiring integration rework. For merchants running older versions, Payment Hub's compatibility layer continues to support back to 2023 R1.
Can we keep our existing payment gateway when we add Payment Hub?
Yes. That's the point. Payment Hub is gateway- and processor-agnostic, you pick whichever of the 19+ supported gateways fits your pricing, your vertical, and your existing merchant relationship. If you're currently running Authorize.Net (which Acumatica discontinued native support for after 2023 R2), Payment Hub continues that integration smoothly. If you're on Worldpay, Fortis, PayTrace, Stripe, or any of the others, Payment Hub fits.
No forced migration, no renegotiated merchant agreement, no lost interchange-rate history. Your existing processor relationship carries forward intact.
Does Payment Hub handle Acumatica's multi-branch and multi-company structures?
Yes. Acumatica's native multi-branch and multi-company organizational structures map directly into Payment Hub's location routing table. Each Acumatica branch / company / warehouse can have its own merchant ID (or share a single MID), its own tax jurisdiction, its own GL account for cash receipts, and its own staff role scope.
Payments originating at any branch route to the correct Acumatica branch + company for posting, with real-time cash application. For organizations using Acumatica Intercompany Accounting, Payment Hub honors the intercompany relationships when cash receipts cross entity boundaries.
Does Payment Hub support Level III interchange optimization for Acumatica B2B transactions?
Yes. Payment Hub automatically enriches every qualifying commercial-card transaction with the 20+ Level III enhanced data fields the card networks require, line items, unit of measure, product codes, sales tax breakdown, freight, destination ZIP, customer code, invoice number. All of these fields are pulled directly from the underlying Acumatica invoice or sales order at the moment of payment.
Typical savings: 0.3%–1.0% per qualifying B2B/B2G transaction. A distributor on Acumatica with $5M in annual B2B card volume typically recovers $15K–$50K in interchange savings annually through Payment Hub's L3 enrichment, with no ERP customization or manual field mapping.
Does the integration require Acumatica customizations we'll have to maintain?
No. The integration uses only Acumatica's standard, documented Web Services API endpoints. No custom Acumatica Customization Projects to maintain, no schema modifications, no unsupported code paths, no third-party database hooks. Your Acumatica version upgrades, Customization Project revisions, and ISV extensions all continue working unchanged.
For multi-branch / multi-company deployments, the configuration work is in Payment Hub's routing table (defining which Acumatica branch maps to which MID / GL / tax setup). That's configuration, not code.
Does this work if our Acumatica is hosted on-premise or in a private cloud?
Yes. Payment Hub works with all three Acumatica deployment models, Acumatica SaaS (hosted by Acumatica), private cloud (hosted by your cloud partner / VAR), and on-premise. For on-premise deployments, Payment Hub reaches your Acumatica instance through the same Web Services API endpoints, typically via outbound-only firewall rules from your Acumatica server.
No inbound firewall ports need to be opened on your network. Clarity is flexible about authentication and network patterns and can accommodate most enterprise security requirements.
How does Payment Hub handle Acumatica's Customer Portal?
Payment Hub can run alongside Acumatica's Customer Portal or replace the payment-facing portion of it entirely. Common pattern: keep Acumatica's Customer Portal for order entry, shipment tracking, and non-payment customer-service features. Use Payment Hub's self-service portal for balance / invoice / payment / aging / saved-methods / autopay / subscription management.
Both portals read the same Acumatica tenant, so customers see consistent data whichever portal they're in. Many deployments use SSO so customers authenticate once and move smoothly between portals.
What's the implementation timeline?
A typical Payment Hub + Acumatica integration goes live in 48 hours once Clarity receives your Acumatica sandbox credentials, your gateway credentials, and your baseline routing configuration (which Acumatica branches / companies / tax jurisdictions map to which merchant accounts). Because the integration uses Acumatica's standard Web Services APIs rather than custom ERP modifications, there's no schema change, no Acumatica-side custom code to maintain, and no version lock.
For larger multi-branch deployments (5+ Acumatica branches / companies), the go-live is staged, pilot with 1–3 branches in the first 48 hours, then add subsequent branches in 24–48 hour batches. The implementation is a flat subscription that includes the integration. Your existing Acumatica license, modules, and customizations stay intact.
Who supports the integration, Clarity or our Acumatica VAR?
Clarity supports the integration directly. Your Acumatica VAR / MSP continues to support the Acumatica platform itself (upgrades, customization, module configuration, training). Payment Hub's support covers the integration layer, payment acceptance, gateway issues, Clarity Connect, L3 enrichment, customer portal, and anything that touches the Payment Hub infrastructure.
Most Acumatica VARs are already familiar with Clarity and work collaboratively on deployments. For Acumatica partners new to Clarity, the integration handoff is straightforward, the Clarity Connect layer is designed to be VAR-friendly with standard API patterns.